-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0
-
mantis
-
sparc
-
solaris_2.6
For Java Plug-in support for deploying Java optional packages (i.e. Java
3D) there should be a change made so users can specify the name (j3dcore.jar) of the jar file(s) used in the optional package. Add a new attribute key (Ex:
Jar-List) to the applets manifest to support this new approach. Right now the Plug-in goes through all the jar files found in the <jre>/lib/ext directory looking for a possible match. This is a performance problem. I've had a number of optional packages installed and it looks like the browser/plugin is hung
when it is checking the jar files. This new way, with the jar file name being known the plugin can process that file right away, instead of having to look at
all the jar files in the <jre>/lib/ext. If the jar does not exist then the
optional package can just be installed or all the jar files can be looked at to try and find a match (current method). We'll have to decide on what to do in this case.
3D) there should be a change made so users can specify the name (j3dcore.jar) of the jar file(s) used in the optional package. Add a new attribute key (Ex:
Jar-List) to the applets manifest to support this new approach. Right now the Plug-in goes through all the jar files found in the <jre>/lib/ext directory looking for a possible match. This is a performance problem. I've had a number of optional packages installed and it looks like the browser/plugin is hung
when it is checking the jar files. This new way, with the jar file name being known the plugin can process that file right away, instead of having to look at
all the jar files in the <jre>/lib/ext. If the jar does not exist then the
optional package can just be installed or all the jar files can be looked at to try and find a match (current method). We'll have to decide on what to do in this case.
- relates to
-
JDK-4684106 REGRESSION: negative effect on deployed applets with optional packages
-
- Resolved
-