16192 - site requiring java tells me m10 is not java enabled

Status: VERIFIED INVALID

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

Description

[wtopp]

i start at http://www.thrall.org/webpac.htm
i select "java webpac"
the next page tells me my browser is not java enabled.
i am running m10 with the java and javascript boxes checked on in
edit/preferences/advanced

Comment 1

[drapeau]

Can you provide more info?  The most useful information here would be the
following:

1) What version of the JDK are you using?  (related to that, have you installed
the Java Plug-In, copied the appropriate DLL's to the Mozilla components
folder?)

2) Have you tried the M11 build?  M11 should be more stable with respect to Java
support, and you should also get the latest JDK (JDK 1.3 Beta).  Note: if you
use JDK 1.3 Beta, you should disable the HotSpot VM.  There is a bug in the 1.3
Beta HotSpot VM that prevents it from working correctly with Mozilla, but the
bug is fixed in later releases and will be fixed for JDK 1.3 when released for
General Availability.

Comment 2

[drapeau]

Got no response from the person reporting the bug; will push off for one more
milestone before closing as an invalid bug (invalid because OJI works in M11 and
subsequent).

Comment 3

[chris hofmann]

move to m14. let me know if fixes are available. thx.

Comment 4

[drapeau]

Copying Stanley Ho on this bug for his sage advice.  In trying to load this
applet, the Java Console reports a "java.lang.ClassFormatError: WebClient (Local
variable name has bad constant pool index)".  Perhaps this applet is illegal
Java bytecode?  It doesn't look like an OJI problem; at worst, it's a JDK
problem, but more likely it's the java bytecode on this applet itself.  The
applet begins to load fine, which is expected behavior of the OJI module with a
Java Plug-in there.

I'd like to mark this bug INVALID, but will hold back until I hear more from
Stanley.

Comment 5

[stanley.ho]

I tried the applet, and it gave me the exception:
java.lang.ClassFormatError: WebClient (Local variable name has bad constant pool 
index)
	at java.lang.ClassLoader.defineClass0(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:592)
	at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:247)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
	at sun.applet.AppletClassLoader.findClass(AppletClassLoader.java:128)
	at 
sun.plugin.security.PluginClassLoader.findClass(PluginClassLoader.java:177)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:301)
	at sun.applet.AppletClassLoader.loadClass(AppletClassLoader.java:108)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:257)
	at sun.applet.AppletClassLoader.loadCode(AppletClassLoader.java:366)
	at sun.applet.AppletPanel.createApplet(AppletPanel.java:579)
	at sun.plugin.AppletViewer.createApplet(AppletViewer.java:1073)
	at sun.applet.AppletPanel.runLoader(AppletPanel.java:515)
	at sun.applet.AppletPanel.run(AppletPanel.java:293)
	at java.lang.Thread.run(Thread.java:484)


This means that the class file format is not invalid for Java 2 JVM. Since there 
have been a lot of enhancement and bug fixes in the Java 2 JVM, it will less 
tolerate invalid class file format. This is not a bug. To resolve the exception, 
simply recompile the Java source files using latest Java compiler should do it.

Comment 6

[drapeau]

Marking the bug as invalid due to comments from Stanley Ho, who works in the
JDK Engineering organization and (presumably) knows what he's talking about. :-)

Comment 7

[Paul Wyskoczka]

Verified per Stanley's comments.