Internet Explorer Problem

[nelsoc]

I have a couple of simple Applets that run fine when I use Netscape, but when I try to view them with Internet Explorer I get this:

Error loading class: three13.three13
java.lang.NoClassDefFoundError
java.lang.ClassNotFoundException: three13.three13
     at com/ms/vm/loader/URLClassLoader.loadClass
     at com/ms/vm/loader/URLClassLoader.loadClass
     at com/ms/applet/AppletPanel.securedClassLoad
     at com/ms/applet/AppletPanel.processSentEvent
     at com/ms/applet/AppletPanel.processSentEvent
     at com/ms/applet/AppletPanel.run
     at java/lang/Thread.run

Is this just because Microsoft hates Java, or is there something I can do to make my Applets run on IE?

Thanks!
Nels

[tom]

Just currious, what did you use to compile your applet?

How does your inner class look like?

Have you tried it with suns appletviewer?

[blahblahblahh]

Just currious, what did you use to compile your applet?

How does your inner class look like?

Have you tried it with suns appletviewer?

...and how have you packaged the classes? And how are you calling them from the HTML? IIRC appletviewer accepts some combinations of syntax that IE doesn't like.

Games published by our own members! Check 'em out!

[nelsoc]

I'm using Sun's NetBeans IDE 3.5.1, and the compiler it uses.

I only have the one class right now. It's called from the HTML as follows:

<P>
<APPLET codebase=.. code="three13/three13.class" width=320 height=200></APPLET>
</P>

That was the code generated for me by NetBeans...

[blahblahblahh]

I'm using Sun's NetBeans IDE 3.5.1, and the compiler it uses.

I only have the one class right now. It's called from the HTML as follows:

<P>
<APPLET codebase=.. code="three13/three13.class" width=320 height=200></APPLET>
</P>

That was the code generated for me by NetBeans...

Try replacing that with

<APPLET code="three13.class" width=320 height=200></APPLET>

using relative paths (..) in the codebase, especially where it's entirely pointless, strikes me as being rather strange. And I have 0 faith in NB to ever get anything right anyway

[oNyx]

IE is the pain :-/

1	<applet archive="Progs.jar" code="Progs.class" width=400 height=450>

Results in: load: class Progs not found

What is the problem? Without using an archive everything works fine... is the IE's default VM really too stupid to understand that?

Do I have to use CABs?

How do I sign 'em? What if that doesn't work? There isn't a way to sign a bunch of class files wich aren't archived right?  :-/

[erikd]

this is what I have in the HTML for CottAGE and that works in IE:

1   2   3   4

<APPLET CODE="cottage.Cottage.class" ARCHIVE="Cottage.jar" WIDTH="224" HEIGHT="288"> <PARAM name="DRIVER" value="mspacman"/> Your browser does not support Java... </APPLET>

(The PARAM tag is to pass parameters to the applet)

I noticed that to get things working, I you need to have a MANIFEST in the jar with the main class, and you *must* compile using -target 1.1 option.

Erik

[oNyx]

Well thanks for the answer... already got that far... but signing sucks... IE just ignores the fact that it's signed. It's IE 5.0 with one vm update wich is years ago. It understands  Swing stuff (obscure)... but it doesn't understand it if it's jar-ed(wtf?). 1.1 stuff works again jar-ed... so heh... <swear word> ms.

We just throw that 1.1 idea into the garbage bin. A whole day wasted for nothing except lots of frustration.

And you can't even buy level 2 digital IDs anymore (20$ a year)... instead you have to buy a level 3 digital ID wich is 400$ for two years (and ofcorse you need another one if you want to support stoneage netscape too... so it's 800$).

And using a self certificate doesn't work... you need to d/l the msvm sdk... install it... and then set a flag with it... on *all* clients. Haha... very funny :/

1.3+, selfcertificate and jar (damn I really hate cabs) was the only way... everything else is just more pain.

Well... just one thing... I'm glad that MS has stopped their Java "support". I'm glad that the future will be without major ms java <f-word>age. I'm looking forward the day MS's proprietary dirt tracks finally disappear.

Thanks for listening

[erikd]

Ouch that sounds bad, yet typically MS.
I fully agree with you. MS has done the right thing to stop supporting what they called 'java' and so should we.