Closed Bug 40519 Opened 25 years ago Closed 24 years ago

Mozilla fails to detect JDK 1.3 installed by itself

Categories

(Core Graveyard :: Java: OJI, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: shrir, Assigned: drapeau)

Details

I did the following: 1. Installed netscape6 without the JRE. (use either a typical install or custom install with 'SUN JRE1.3' unselected) 2. Then I manually installed Sun's JRE( with Java Plugin 1.3) available here: http://java.sun.com/j2se/1.3/jre/download-windows.html 3. Started mozilla and launched a page with java applet,for instance,http://java.sun.com/applets/other/Bubbles/index.html 4. Mozilla did not load the applet on the page. 5.Only if I manually add the three plugin files (npjava11.dll, npjava12.dll and npjava32.dll) from the JRE installation's '/bin' folder to the plugins folder under mozilla then the applet loads fine. On the other hand, after the JRE installs, I see that the 3 plugin files get added automatically to the plugins folder on 4.x installation on the same machine. I would expect the same to happen with mozilla too.
Update from Andrei: the fix he put in (at my request!) to prevent the old Sun Nav4 JVM plug-in from crashing Mozilla prevents Mozilla from loading any Java VM from the Nav4 plugins directory. So if: (1) JDK 1.3 when installed independently only installs itself in the Nav4 plugins directory and doesn't look for a Mozilla plugins directory, and (2) Mozilla when it starts up doesn't go looking to see if a JDK 1.3 has been installed somewhere while Mozilla wasn't in use ... ... then it makes complete sense that Mozilla fails to detect JDK 1.3 installed by itself. Andrei's exact email: Eric Krock wrote: > > Andrei, we've noticed that if you install N6 without Java, then install > standalone JDK 1.3 later, N6 doesn't realize that JDK is now available. Is > it possible that this is because of the fix we had you put in to prevent > the loading of the old Nav4 Sun JVM binary? Or did that fix only prevent > loading of the Nav4 Sun JVM binary and not the new JDK 1.3 binary? The latter. More precise, that fix prevents loading Java plugin from 4.x installation Plugins dir, regardless the version. I suspect that JDK 1.3 installer just does not copy the Java plugin into Mozilla plugins dir, but may be it copies it into 4.x Plugins dir path to which it most probably finds in the registry. Andrei
I claim that this is not a Mozilla bug, but rather a Sun java RFE. What you're saying is that when one installs the Sun JRE, you would like it to ask "Would you like the JRE installer to install the necessary plugins for Mozilla/Netscape 6, too?" That's a reasonable request to ask of Sun. I'm copying Stanley Ho from Java Software on this so he's aware, but I would recommend you also file this as a bug against the Java software distribution, at http://java.sun.com/cgi-bin/bugreport.cgi. Closing as "INVALID". Please re-open if you disagree, Shrirang. The feature request is valid; I just believe that the place to file the bug is elsewhere.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Sun bug not ours marking as invalid.
Status: RESOLVED → VERIFIED
Hey, check this out: Java Software fixed this! When you install the JRE 1.3.0_01, it will look in the Windows registry for signs of Mozilla/Netscape 6, and when found, will automatically copy the appropriate DLL's into that browser's plugins directory. Pretty cool, huh? Try it with a recent commercial nightly build, and behold. Or, install Mozilla, then separately install the JRE 1.3.0_01 (available internally at Netscape now, externally soon). Does that mean we get to mark it FIXED?
Yes, this is working now. I tried this with yesterday's build and it works.Reopening, and marking it as FIXED.
Status: VERIFIED → REOPENED
Resolution: INVALID → ---
fixed
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
verified fixed.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.