>> We have an ancient application (an old service processor for proprietary
>> hardware) that is manageable only by a browser running Java 1.2.
Why do you say that? What Java 1.2 bug* does it rely on?
* That is the only thing I can think of, that would lock
a Java application or applet to a specific version of
the JRE.
>Can you not use appletviewer from the JDK?
..also as used by Java web start (for launching
applets*). JWS is also good for JRE versioning**.
* <http://www.physci.org/jws/#jtest>
** <http://www.physci.org/jws/version.html#earlier>

Signature
Andrew Thompson
http://www.athompson.info/andrew/
Will - 26 Jun 2007 22:55 GMT
>>> We have an ancient application (an old service processor for proprietary
>>> hardware) that is manageable only by a browser running Java 1.2.
>
> Why do you say that? What Java 1.2 bug* does it rely on?
They wrote the application with hard-wired logic to stop working on any JVM
that is not 1.2.
I'm not defending it. I'm trying to work around it.
> * That is the only thing I can think of, that would lock
> a Java application or applet to a specific version of
> the JRE.
>
>>Can you not use appletviewer from the JDK?
I'll try it.

Signature
Will
Joshua Cranmer - 27 Jun 2007 21:54 GMT
> They wrote the application with hard-wired logic to stop working on any
> JVM that is not 1.2.
I assume that the hard-wired logic is equivalent to System.getProperty
("java.version").equals("1.2"); if so, then maybe running with -
Djava.version=1.2 might fix it.