richp
asked on
Applet problem with IE5
I have a client who upgrade his browser to IE 5 and the latest java vm but he still receives this error:
com.ms.lang.VerifyErrorEx: com/island/chicago/inlet/I nlet.jbIni t: type
mismatch: actual type jclass/bwt/JCTabButton, expected type
jclass/base/BaseComponent
at com/island/chicago/inlet/I nlet.init
at com/ms/applet/AppletPanel. securedCal l0
at com/ms/applet/AppletPanel. securedCal l
at com/ms/applet/AppletPanel. processSen tEvent
at com/ms/applet/AppletPanel. processSen tEvent
at com/ms/applet/AppletPanel. run
at java/lang/Thread.run
Several other people running the same version browser and java vm do not have a problem. He's running windows NT.
Is there something I should look at in NT as the cause of this problem? Has anyone encountered this problem before?
Thanks,
Rich
com.ms.lang.VerifyErrorEx:
mismatch: actual type jclass/bwt/JCTabButton, expected type
jclass/base/BaseComponent
at com/island/chicago/inlet/I
at com/ms/applet/AppletPanel.
at com/ms/applet/AppletPanel.
at com/ms/applet/AppletPanel.
at com/ms/applet/AppletPanel.
at com/ms/applet/AppletPanel.
at java/lang/Thread.run
Several other people running the same version browser and java vm do not have a problem. He's running windows NT.
Is there something I should look at in NT as the cause of this problem? Has anyone encountered this problem before?
Thanks,
Rich
I suppose that all the other people have installed JBuilder ...
ASKER
This was on the client side using only a browser.
I thought if a client has the same browser version and virtual machine the applet should run and it does for the majority of the clients.
I thought if a client has the same browser version and virtual machine the applet should run and it does for the majority of the clients.
both IE and NN on Windows will load classes from the system classpath automaticly. so if your applet uses some borland classes some browsers may load them from the local classpath.
just a guess :)
just a guess :)
ASKER
Wouldn't those classes be loaded from the jar file? If not, are you saying that user may have a local copy of a non-compatible borland class?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It was a borland class but a klgroup class. The user had another jar file in his classpath which contained non-compatible jclass class files.