 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Java Forum / First Aid / June 2006How to cause IE to use specific plugin?
Hello, We have an applet, that was working properly in all plugin versions from 1.4.2_06 till 1.5.0_05, but has some problem in 1.5.0_06 and _07 It is launched by HTML that should restrict it to use 1.4.2_06 plugin version, but for some reason if any 1.5 version is installed on the computer it uses 1.5 instead. I was trying different things to cause IE to use 1.4 plugin, but didn't succeded. Although browser's option says "Use Java 2 v 1.4.2_06 for <applet>" and in HTML written: <OBJECT classid = "clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA" codebase = "http://java.sun.com/update/1.4.2/jinstall-1_4_2_06-windows-i586.cab#Version=1,4,2,60" This was working with 1.4 versions, but it is different with 1.5 - applet is allways launched in 1.5 plugin and 1.5's control panel doesn't even show 1.4 version in the "Java applet runtime settings" - only in "Java application runtime settings". So, the question is - how to cause the applet to run in 1.4 plugin if 1.5 version is installed? Any help will be highly appreciated. Maxim Golubitsky ... > I was trying different things to cause IE to use 1.4 plugin, but didn't > succeded. Although browser's option says "Use Java 2 v 1.4.2_06 for > <applet>" and in HTML written: > <OBJECT classid = "clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA" > codebase = > "http://java.sun.com/update/1.4.2/jinstall-1_4_2_06-windows-i586.cab#Version=1,4,2,60" This list... http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/autodl-fil es.html States "Note that not every release of the JRE has an associated .cab file for autodownload." If you copy paste one of those URL's in the list into your brower's address bar and try and fetch it you should see a file download dialog. ..Now change the address to the Java version you are specifiying (the complete URL in the codebase) and try it again. Andrew T. andrewthommo@gmail.com (): > ... > > I was trying different things to cause IE to use 1.4 plugin, but didn't [quoted text clipped - 15 lines] > > Andrew T. >From the link that you provided I learned that autodownloading of JRE version that I specified will not work. But my question is why applet is not running in 1.4 JRE that already installed in the system and specifically stated in HTML if 1.5 version is present too? > andrewthommo@gmail.com (): > > > ... > > > I was trying different things to cause IE to use 1.4 plugin, but didn't > > > succeded. .. > > ..."Note that not every release of the JRE has an associated .cab > > file for autodownload." ... > From the link that you provided I learned that autodownloading of JRE > version that I specified will not work. But my question is why applet > is not running in 1.4 JRE that already installed in the system and > specifically stated in HTML if 1.5 version is present too? My theory is this. The object element starts by telling the JVM nonsense about a JRE that does not exist. Having not found that version, Java does the best it can to accommodate the end user's needs - in a less than predictable way. Change your reference to a download .CAB that exists. If that does not work for versioning, I would be willing to revisit this problem. Andrew T. I changed everything from _06 to _03 (classid and codebase) but it still doesn't load applet in 1.4 version. I also tried to use regular <APPLET> tag with the same result. > I changed everything from _06 to _03 (classid and codebase) but it > still doesn't load applet in 1.4 version. OK. That is beginning to sound like a bug. Can you put up a public version so that we can confirm your results? (It does not need to be a 'real' applet - perhaps just a simple one that reports the JRE version) An URL that demonstrates the problem is more likely to get attention (and I can do some quick checks on the HTML). >...I also tried to use regular > <APPLET> tag with the same result. Ignore the applet element for the moment - it was never designed to do versioning. It is the OBJECT element not doing proper versioning that is the real concern. Andrew T. andrewthommo@gmail.com (): > > I changed everything from _06 to _03 (classid and codebase) but it > > still doesn't load applet in 1.4 version. [quoted text clipped - 15 lines] > > Andrew T. Here is the URL of our real applet: http://212.29.213.34/tradetrac.html You can see the JRE version from the java console. Today I discovered, that this behavior happens most of the time but not allways. I found 2 machines where applet is being loaded in the correct JRE. I unsuccefully tried to find anything common between them that also will be different from the machines where the problem exists. Let me know if you want anything about machines where it happens / not happens. Maxim > andrewthommo@gmail.com (): (1.4.2_06 not available as auto-download .CAB) > > > I changed everything from _06 to _03 (classid and codebase) but it > > > still doesn't load applet in 1.4 version. ... > > Can you put up a public version so that we can confirm your > > results? .. > Here is the URL of our real applet: http://212.29.213.34/tradetrac.html That page is requesting 1.4.2_06 ... <OBJECT classid = "clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA" codebase = "http://java.sun.com/update/1.4.2/jinstall-1_4_2_06-windows-i586.cab#Version=1,4,2,60" WIDTH = 0 HEIGHT = 0 NAME = "STPlatform" ALIGN = middle > ... Andrew T. andrewthommo@gmail.com (): > > andrewthommo@gmail.com (): > [quoted text clipped - 17 lines] > > Andrew T. I wrote today that the problematic behavior happens not all the time. Actually, today they called me from QA to ask why when they run the applet it asks to install 1.4 version if there is already 1.5 version installed. So I seen it myself: on the machine having JRE 1.5.0_05 there was an automatic request to install 1.4.2_06 that perfectly worked and it continue to run in this version. When you pointed me to the list of available installations I thought that maybe SUN removed some of them, because I know that in the past it was available. But as I say, it worked today perfectly, so I'm sure that the problem isn't micro version. Still, if you insist, here is changed version: http://212.29.213.34/Test03.html > andrewthommo@gmail.com (): > > > > andrewthommo@gmail.com (): > > > > (1.4.2_06 not available as auto-download .CAB) * > > > Here is the URL of our real applet: http://212.29.213.34/tradetrac.html ... > I wrote today that the problematic behavior happens not all the time. > Actually, today they called me from QA to ask why when they run the > applet it asks > to install 1.4 version if there is already 1.5 version installed. > So I seen it myself: on the machine having JRE 1.5.0_05 there was an > automatic request to install 1.4.2_06 that perfectly worked There is something bizarre going on here. Although _06 was not listed on the downlaoad page, and a 'drect fetch' on the URL failed, today I first tried that _06 URL again (again failure), but then I tried _05, and got a /download/ box for version _06! >..and it > continue to run in this version. When you pointed me to the list of > available installations I thought that maybe SUN removed some of them, That would not be /too/ strange for Sun, though I am less confident _06 is not available now - it would make no sense to offer downloads of 1-4-2_01/02/03 (all relatively crappy versions with a security bug) but not offer later versions like _06. > because I know that in the past it was available. I'll trust you on that. >...But as I say, it > worked today perfectly, so I'm sure that the problem isn't micro > version. ...hmmm. I think it has *something* to do with the appearing/disappearing _06. I'm just not sure what is going on. >...Still, if you insist, here is changed version: > http://212.29.213.34/Test03.html That version did predictably load 1.4.2_03. I got a dialog advising me to reboot (or something, which I ingored) then was prompted by a dialog to refresh the page for the _03 JRE - the console confirmed the applet was now running in 1.4.2_03. So we have 1 'failure to reproduce the problem' using a .CAB that seemingly is easily accessed.. I suspect this 1.4.2_03 version would also work flawlessly on other browsers. The question mark is the 1.4.2_06 version - why is it not available for a direct fetch? Is it actually being removed and again being made available? Previously I thought this problem was caused by a missing _06 version, but it seems it is not that straightforward. Andrew T. andrewthommo@gmail.com (): > > andrewthommo@gmail.com (): > > [quoted text clipped - 60 lines] > > Andrew T. I think that problem might be in deployment.properties file. I'll check this version... Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.