When I run an applet out of Eclipse, I am getting this error: Warning: Cannot convert string "-b&h-lucida-medium-r-normal-sans-*-140-*-*-p-*-iso8859-1" to type FontStruct java.lang.UnsupportedClassVersionError: applets/M03_01_04/Applet (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) 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 java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:282) at sun.applet.AppletClassLoader.loadClass(AppletClassLoader.java:123) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at sun.applet.AppletClassLoader.loadCode(AppletClassLoader.java:595) at sun.applet.AppletPanel.createApplet(AppletPanel.java:621) at sun.applet.AppletPanel.runLoader(AppletPanel.java:550) at sun.applet.AppletPanel.run(AppletPanel.java:301) at java.lang.Thread.run(Thread.java:534) The applet itself looks very weird, the font it used seems very wrong.
Created attachment 169628 [details] screenshot of applet viewer
I didn't had the problem with sun-jdk-1.6.0.07.
Ok, the problem was probably that I forget to update the path to JDK 1.6 (because I had set it to 1.6.0.07 before) and it probably has used the old JDK 1.4. Though, I am getting now again the strange error "Selection does not contain a Java applet", see bug #243466. But this is another bug and not related here. I am not sure if this should be considered as a bug (if Eclipse should update such path automatically) or as invalid.
Either way, that would probably be an eclipse upstream problem, and if you wish to report it, have a look through their existing bugs at [1] first, and then file it there. Bear in mind, this may also have been fixed in eclipse 3.4 or 3.3 (since in bug 243466 you mention you're still using 3.2.1). [1] https://bugs.eclipse.org/bugs/