P5
Java extensions like Java Advanced Imaging (JAI) Java 3D now go into the runtime jre/lib/ext.
When customers use a particular version(for their deliverables) they cannot upgrade their systems to test a newer version co-existing with the older version using just one JRE.
They have to either use another JRE OR have both the versions installed outside the JRE with classpath settings.
Customers may use MORE than one extension at a time, java3d, jmf, jai and keeping up with the extension version changes gets difficult.
there is a runtime option specified as -Djava.ext.dirs= where you can specify where to look for the extension jar files.However, we can find no place
to set this property as a defualt, so you have to supply -Djava.ext.dirs=...
on each and every command line. Can we have something like whats done for -classpath or similar, the java.ext.dir value can have a default value OR picked from the environment if exist and not defined at the command line ?
We have customers who are facing this problem using different versions of our product. The need development to use one version and testing to use another but have a common JRE.
When customers use a particular version(for their deliverables) they cannot upgrade their systems to test a newer version co-existing with the older version using just one JRE.
They have to either use another JRE OR have both the versions installed outside the JRE with classpath settings.
Customers may use MORE than one extension at a time, java3d, jmf, jai and keeping up with the extension version changes gets difficult.
there is a runtime option specified as -Djava.ext.dirs= where you can specify where to look for the extension jar files.However, we can find no place
to set this property as a defualt, so you have to supply -Djava.ext.dirs=...
on each and every command line. Can we have something like whats done for -classpath or similar, the java.ext.dir value can have a default value OR picked from the environment if exist and not defined at the command line ?
We have customers who are facing this problem using different versions of our product. The need development to use one version and testing to use another but have a common JRE.