631242 - Java Embedded Plugin not needed anymore

Status: RESOLVED INVALID

(Plugins Graveyard :: Java (Java Embedding Plugin), defect)

Description

[Ángel Eduardo]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13

At least on my system (with Snow Leopard 10.6.6, Java(TM) SE Runtime Environment (build 1.6.0_22-b04-307-10M3261), using the Java Embedding Plugin (as distributed with Firefox 3.6.13) makes all pages (like NASA WorldWind, as provided in URL) use the old plugin (so no JNLP support, for instance). Removing MRJPlugin.plugin and JavaEmbeddingPlugin.bundle from /Firefox.app/Contents/MacOS/plugins makes Firefox use the "Java Plug-In 2 for NPAPI Browsers" as it should

Reproducible: Always

Steps to Reproduce:
1. Enter in the provided URL
Actual Results:  
Plugin displays "Click here to get the new Java Plug-In"

Expected Results:  
Page should load the NASA WorldWind application (it will appear blank with text at the bottom instead of appearing the globe, but that's Java problem, not Firefox)

Comment 1

[Ángel Eduardo]

I forgot to add that merely disabling the "Java Embedding Plugin 0.9.7.4  MRJ Plugin version 1.0-JEP-0.9.7.4" doesn't make Java use the new plugin (in fact, Java ceases to work) so that's why removing is necessary.

Comment 2

[Steven Michaud [:smichaud] (Retired)]

The JEP is definitely still needed on the branches.

To use Apple's Java Plugin2 instead (on OS X 10.5.8 and 10.6.X) you
need to remove the following two items from your Firefox distro's
Contents/MacOS/plugins directory:

JavaEmbeddingPlugin.bundle
MRJPlugin.plugin

Comment 3

[Steven Michaud [:smichaud] (Retired)]

There may be some things that the JEP can't do which Apple's Java Plugin2 can do.  But Apple's Java Plugin2 also has lots of problems that the JEP doesn't have.  See bug 554103.

Comment 4

[Ángel Eduardo]

Thanks for your comments.

As you can see, I suggested the same to enable the Java 2 plugin, but I hoped for a better way to disable it. Also, I don't know which problems do the Java 2 plugin have, but unfortunately this is the way Safari,  Chrome AND Firefox 4 does things, and also the only way to have Plugin2 features (like JNLP or compressed jars) which we need for our (business) applets, so if we don't want to maintain two behaviors, this is the only way I know.

So, if you suggest the same (removing those directories), this is also the way we'll tell our clients / automate things.

Thanks a lot!