We're providing a new way for plugins to detect embedded installations of Gecko, and the Java plugin installer needs to use this new mechanism. peterlubczynski worked on a preliminary version of this, but we're cooking up a variation on it for the summer releases. cc'ing Peter for a link to the technical details. Since this installer issue blocks embedded Gecko from running Java at all (unless you copy the files around by hand), I'm marking severity blocker.

Copying Java Plug-In folks and OJI module owner. We've been discussing something similar in OJI engineering meetings, I believe; Stanley, Ed, and Peter L. should hook up to figure out the right thing to do. Stanley and/or Jim should be able to give us a notion of whether it's possible to deliver a fix soon enough for Gecko embedding consumers. Peter: will you please contact Ed and Stanley by email and tell them the proposal? (edburns@eng.sun.com, stanleyh@eng.sun.com) If you need help, let me know.

Isn't bug 66840 about this? Please explain the difference.

In http://bugscape.mcom.com/show_bug.cgi?id=2052 (intenal link, sorry) it's argued that they aren't the same. Both are long bugs, so you could be right...

While we're adding internal links, here's the bug that shows the implementation. I'll write-up a short doc shortly. http://bugscape.mcom.com/show_bug.cgi?id=3863

Peter, Phil: Stanley and Jim can't see the Netscape-internal links, so they can't see the work that they may need to do in order to make Java Plug-In installer work correctly with embedded Gecko installations. Peter, can you post your suggested plan to this bug? That way, Jim and Stanley can evaluate and reply with whether they're willing/able to do it. If they're not, then perhaps we can brainstorm a way to work around it (previously, we've taken the Java Plug-In DLL's separately from the JRE release and put them in the Netscape 6 installer; we could do that again, I suppose, for this release).

Java doesnt work for me at all, sure I copied the java files to the plug-ins folder so now instead of saying I need the plugin it just crashes.

Bug 66840 is similar to this bug, but slightly different. Here's the difference: Bug 66840 claims that the registry key used for Mozilla has changed its name; the current JRE installer looks for the old name, and thus no longer knows where to copy the Java Plug-In DLL's into Mozilla installations. This bug is about yet another Mozilla-based application, that uses yet another Windows registry key. Even if the JRE installer were updated to use the new key described in 66840, that updated JRE installer wouldn't work with embedded Gecko installations described in *this* bug. Anyway, having said that, I don't know if Java Software will be willing to supply a modified JRE installer. See Stanley Ho's comments in bug 66840 for details, and an alternate solution he offers. His alternate solution, which would apply here as well, is to create a .XPI that contains just the plug-in DLL's, and have that XPI copy them into whereever the browser/gecko app is installed. I believe that solution also handles the case in which you've installed Mozilla/Gecko but with no Java, and then you later go to a page that requires Java (therefore launching the plugin downloader). In that case, you still have a .XPI file to download, and that .XPI could use the new key scheme to determine where to copy the .DLL's. Is that workable? The difference, basically, is whether Java Software does the work of updating its JRE installer, or Netscape/Gecko vendor makes a .XPI containing just the Java Plug-In binaries.

The "opposite" of this bug is: http://bugzilla.mozilla.org/show_bug.cgi?id=78150 [RFE] Include OJI plugin installation path in plugin scan Until the Java installer is fixed, let's go and find it instead of just failing.

Changing ownership to Jim Melvin; this is not a bug in the browser but in the Java Plug-In or JRE installer.

Making a guess at priority of this work. Jim, forgive me if I guessed wrongly (it's really your role to assign priority to this bug as it's currently assigned to you). Also, will you please accept this bug?

SPAM: reassigning all OJI bugs to new OJI QA, pmac ( 227 bugs)

See bug 75651 which contradicts this one in the direction we should head on this. One of them should be ceratinly be made WONTFIX. The good question is which.

*** Bug 110870 has been marked as a duplicate of this bug. ***

I believe I just encountered this problem with Mozilla 0.9.7 on Windows 98. I went to a page that required the Java plug-in and I was prompted to install it, by Mozilla. I proceeded with the installation which downloaded JRE 1.3.1 from Netscape and ran the JRE installer. I chose the default installation for the JRE installation and after the installation, Mozilla was NOT updated with the JRE plug-in. Peace... Tom

http://gemal.dk/mozilla/java.html will tell you how to get Java working in Mozilla

Also see bug 100393.

aint 120914 and 123832 dupes of this ?

Just got around this in 0.9.8. on Win98 se. Tried all the dll copy tricks mentioned in #100580 which is apparently the same thing. Only it didn't work for me, all I got was 'Starting applet ...' on status bar and then nothing though everything else still worked normally. Until I finally uninstalled the JRE and went to the applet page clicked the install icon once again and so on. Still not working so I decided to copy npoji600.dll one last time. Strangely enough the applet worked without problems after booting Mozilla again. To me there is little doubt, that in addition to the dll copy problem, Mozilla can't handle a situation where the Java plugin already is in place when Mozilla is installed. Hope this helps. Matti

*** Bug 131292 has been marked as a duplicate of this bug. ***

*** Bug 133623 has been marked as a duplicate of this bug. ***

After doing the copy dance Java seemed to work for the most part. I do get a dialog box Saying "An unknown erroe occured while attempting to open requested page" when clicking a link that opens a Java spawned window. for example a player card in an ESPN fantasy sports game like this one: javascript:newWin('request.dll?PLAYERCARD&nPlayerID=750') and then the window will open is if nothing had been wrong in the first place. adc6r

*** Bug 133752 has been marked as a duplicate of this bug. ***

*** Bug 135618 has been marked as a duplicate of this bug. ***

Is this now working with Mozilla 1.0?

Yes, at least with Java Plugin 1.4. Tested with Windows98 and WindowsME.

doesnt this work now ?

Sorry, I don't have clean system where I can test a brand new installation - I'm using Mozilla on all my computers since May ;-)

reassign to me

This bug has been fixed on JRE1.4.2