Closed Bug 275200 Opened 20 years ago Closed 20 years ago

tells me it needs plug-in sun java J2SE50, and installs it. When firefox is restarted, still says need plug-in

Categories

(Toolkit Graveyard :: Plugin Finder Service, defect, P1)

x86
All

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: peter.brennan, Assigned: doronr)

References

()

Details

 
Do you have Java disabled in Tools - Options - Web Features? (bug 261031)
I am seeing the same thing, and I do have Java turned on.

http://java.sun.com/products/plugin/1.5.0/demos/plugin/applets/BarChart/example
1.html

It keeps asking me to reinstall J2SE50.
(In reply to comment #2)
> I am seeing the same thing, and I do have Java turned on.
> 
> http://java.sun.com/products/plugin/1.5.0/demos/plugin/applets/BarChart/example
> 1.html
> 
> It keeps asking me to reinstall J2SE50.

What operating system are you on?  Does installing it by downloading an
installer from java.com work?
(In reply to comment #0)
>  

I'm seeing the same issue.  I did try installing the JRE 1.5 Update 1 "outside"
of FireFox and the same behavior was observed.

I'm running Windows XP SP1

BTW JRE 1.5 Update 1 does work O.K. with IE.  Please note,  I'm NOT knocking
FireFox in any way, I simply wanted to note that the JRE 1.5 Update 1 does work
in another browser.

I also tried JRE 1.5 (the version prior to JSR 1.5 Update 1) and saw the same
behavior.
if the standalone installer fails, then this is not a plugin finder service
issue but a problem with Sun's installer.
(In reply to comment #5)
> if the standalone installer fails, then this is not a plugin finder service
> issue but a problem with Sun's installer.

I did not say that the standalone installer failed.  The standalone installer
worked just fine.  What I did say was that even when the Java was installed
(using the standalone installer), FireFox was not able to detect and/or use it
as a plugin.

This seems to be site specific, as I was on another site this morning (which
requires Java) and it worked fine (using FireFox) and the installed 1.5.0_1 JRE.

Unfortunately, both sites are internal, so I can't point you to them.

If I get any more "clues", I'll post them!
can you post the applet markup used in both sites?
The issue here is that we have pages looking like this:

<EMBED type="application/x-java-applet;jpi-version=1.4.2_05"

and the 1.5 JVM does not register for that mimetype, yet the pfs backend returns
the Java 1.5 plugin info.

This has been reported before and making this the bug to cover the issue for now.
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 98 → All
Priority: -- → P1
Version: 1.0 Branch → Trunk
*** Bug 269990 has been marked as a duplicate of this bug. ***
Solutions are:

1) make the pfs only return Java 1.5 for the mimetypes it registers for
2) make mozilla force java for certain mimetypes even if it doesn't register for it.
2 better be as a fallback and not by default.
I chose option 1, the plugin finder service now offers java only for mimetypes
that match:

/^application\/x-java-((applet|bean)(;jpi-version=1\.5|;version=(1\.(1(\.[1-3])?|(2|4)(\.[1-2])?|3(\.1)?|5)))?|vm)$/

Oh, the joy of regexps :)

I'm going to mark this Fixed, as I don't think we want to start handing the java
plugin content it didn't register for. Sites really should not require version
numbers that specific to begin with.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
I may be wrong but that solution doesn't look like its future proof! What 
happens when there is a new version of java (which there already is 
https://mustang.dev.java.net/)?
(In reply to comment #13)
> I may be wrong but that solution doesn't look like its future proof! What 
> happens when there is a new version of java (which there already is 
> https://mustang.dev.java.net/)?

If Sun updates the XPI, then we have to update the backend.  Luckily we don't
need the mimetypes on the client, so updating is a cinch (the wonder of web apps).
Product: Firefox → Toolkit
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.