Using a NON-DEBUG build of Mozilla from Tuesday 23 May 2000, and the Java Plugin from Stanley from Monday 22 May 2000, I visited the page <http://www.timewarner.com/> The applet doesn't run and I get this error in the java console: java.lang.ClassFormatError: OCVscroll (Illegal UTF8 string in constant pool) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at sun.applet.AppletClassLoader.findClass(Unknown Source) at sun.plugin.security.PluginClassLoader.findClass (PluginClassLoader.java:175) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.applet.AppletClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.applet.AppletClassLoader.loadCode(Unknown Source) at sun.applet.AppletPanel.createApplet(Unknown Source) at sun.plugin.AppletViewer.createApplet(AppletViewer.java:1101) at sun.applet.AppletPanel.runLoader(Unknown Source) at sun.applet.AppletPanel.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
*** Bug 41159 has been marked as a duplicate of this bug. ***
This error occurs when an applet class file was loaded into the JVM, and the class file format was recognized as bad format. Since most of the applets in the internet are JDK 1.0.x or JDK 1.1.x based, it was usually compiled with old Java compiler and executed in JVM that is 1.1 based in the browser. However, in Netscape 6, JDK 1.3 is used instead, it comes with Hotspot which supports the latest Java specification. It means that it should be more comfront to the specification than the browser default JVM, and it is less tolerate to bad class file format than the browser JVM as well. Therefore, if applet is compiled using old Java compiler and the class file format is not well-formed, then this error will occur. To avoid this problem, developers should recompile the applet with the latest Java compiler, and it should work. This is not really a bug in the JDK in Netscape 6, and it will not be fixed.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WONTFIX
Pretty clear statement. Maybe the JVM will be improved yet for backwards compatiblity? Owner, consider marking this 'verified'.
let me do it..thanks!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.