> >>I am using Jython 2.1a1 and JDK (from Sun) 1.3.1
> >... and I believe 1.3.1 is the real problem. Even if it isn't, I
> >strongly doubt you can make java1 applets with a java2 JVM. You will
> >need to get hold of and install a JDK1.1 and use that when running
>I'm wondering if there are any sensible solutions to this.
>Can the 1.1 JDK coexist with a 1.3?
It can. I have JDK1.1.7A, JDK1.2.1, JDK1.3, JDK1.4, IBMJava1.3 and
MS-SDK4.0 all installed in the same directory.
Some hints (for windows) off the top of my head include:
- I don't set PATH or CLASSPATH in the controlpanel. Instead I have some
small .bat scripts that let me choose java versions.
- When installing a Java2 from javasoft, I *always* remove the java.exe
file in the windows system directory (c:\WINNT\system32 IIRC).
>I had understood that the purpose of the "Java plugin" that
>now comes bundled with the 1.3.x distribution kit was for
>this reason: you can't count on the browser, but you can
>add a plugin to take care of it. I haven't had any joy
>making that work, however. Is there something special one
>can do - thus enabling a 1.3-built Applet to run? i've
>sometimes detected that the plugin is active, but I seem
>never to have gotten it to work for a Jython-built applet.
Sorry, I have no experience with the plugin. Anyone else?
I think it is possible to make a sandboxed plugin applets, but not all
the infrastructure is in place for applets that want to move outside the
>I don't believe this compatibility headache is unique to
>Jython, but the situation's not going to get better: Sun's
>started the end-of-life track on the 1.1 JDK (thus "continue
>to build with 1.1" is not going to remain a viable story).
When java1 applets are the goal, I doubt there is any alternatives. We
may be able toi improve the situation slightly, so that it isn't
necessary to have jython installed with the jdk1.1. But the jdk1.1 class
files (classes.zip) must still be available when building applets.