At 00:53 12/24/99 -0500, Linda Lincoln wrote:
>Perhaps, but some additional information: When I point netscape-navigator at
>the same HTML file it runs the applet without error or complaint (arguments
netscape has a 1.1 vm. (1.1.5 iirc)
>and all). I would expect this kind of behaviour from a Sun demo app. (It's
>been thoroughly tested, I suppose) I think it points to a problem with
>Blackdown's appletviewer implementation.I am running Redhat 5.1 (Manhattan),
>and glibc 2.0 and JDK 1.2.pre v2.
this is a 1.2 vm. (I'll ignore the question of whether this combo is supposed
to work... I somehow doubt it since the glibc requirement for 1.2pre3 is
glibc 2.1.2...)
>Also, the applet's classes had to be recompiled to run properly. (By that I
>mean not crash).
thereby changing some of the signatures in the applet's class files to reflect
the classes in the 1.2 rt.jar. I would not expect something compiled against
the 1.1 libraries to function flawlessly against the 1.2 libraries if it
involves any of the areas that underwent high churn from 1.1 to 1.2 (i.e.
security, which is involved in your exception.)
>From the standpoint of portability considerations this leaves a big break in
>the compile once run anywhere ideal. Users can not be required to recompile
>an app before it loads in their browser.
the break from JDK1.1 to Java2 is painfully larger than it should have been.
WORA across this barrier is limited. I believe this is why Sun's marketing
did some pro-active spin control and renamed the JDK1.2 to Java2 - they
wanted to push the idea that this was a version boundary, not a point
release. (What they'll for jdk 2.0 is going to be fun to watch ;)
cabbey at home dot net <*> http://members.home.net/cabbey
I want a binary interface to the brain!
Today's opto-mechanical digital interfaces are just too slow!
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
