Microsoft JVM troubles
Hi all,
forgive me if this question has been asked before, but I couldn't find anything.
The problem is the following: I have a client interface in Java, compiled with j2sdk-1.4.2.08. I create CAB-files and JAR-files to store this applet in, and in the HTML-page the applet tag has both the archive= and cabbase= attributes.
When one uses the Sun JVM in Internet Explorer, all is well and everything runs fine (as expected :-) ). When one uses Microsoft's JVM 1.1.4, the applet is not loaded, and the main class generates a class-not-found error. Do I need to recompile the applet with -target1.1 (or what is the exact command line switch)? Would that solve this problem?
I am pushing my customer to start using the Sun JVM on all of their machines, but (we're talking about 600 machines here) on about 95% of their machines it's still the above mentioned Microsoft JVM.
Any help would really be appreciated,
TIA,
STefan
[974 byte] By [
Stef68a] at [2007-10-1 23:05:12]
The microsoft JVM implements a very VERY old version of Java -- and not even completely. The version of Java it supports is 1.1, meaning that none of the classes that were introduced in version 1.2 or later cannot be used. This includes, among other classes, the swing API (with the JApplet class and the collections framework (lists, maps and stuff). If you have used these classes in the worst case the only way to make the program work in the MSJVM is by changing the code.
For instance, if you use swing you need to deploy the library with your program. A version that works in 1.1 can be downloaded from http://java.sun.com/products/archive/index.html
:-) well, in IT-terms this applet is VERY old as well - it's origins lie in 1998. So I am not using any classes past 1.2, which means I shouldn't have a problem. The problem is that the error message from the MS JVM is class not found, which seems a bit odd if this is indeed the problem. Then again, we are talking Microsoft here ;-)))
Tonight I'll recompile and distribute the application to the customer, then we'll see if it works or not.
Thanks,
Stefan
Don't know. It happens at the customers site, and all they sent me was the message class not found. It happens with the microsoft JVM, so I just finished compiling for 1.1 (for once having a really old piece of code has it's advantages: without even one glitch ;-) ).
I'll send it to my client, then they can test tomorrow and we'll see. The super classes are in a second package, downloaded separately, which is still the same as 5 years ago. So that should not be the problem.
Thanks for the tip though, I'll keep it in mind!
Cheers,
Stefan
