JDK-6641969 : Optimize bundles.xml
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: x86
  • Submitted: 2007-12-14
  • Updated: 2010-09-17
  • Resolved: 2008-01-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
6u10 b10Fixed 7Fixed
Currently for many workloads downloaded java kernel bundles are almost not used (i.e. only small fraction of bundle content is actually needed to execute application).

Downloading more than needed clearly has negative impact on time needed to start application.
bundles.xml needs to be optimized to decrease download size.

SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6641969/

EVALUATION Primary goal is to decrease footprint for small applications and applets. We can assume that at least on first run graphical application is used in majority of cases. Therefore several typical scenario can be considered: 1) pure AWT applet 2) small Webstart application 3) FX demo app 4) small swing application run from jar etc. Based on analysis of what is needed for different applications and recent improvements in the j2se codebase number of improvements are possible. Some examples: 1) Most of application need only few security or xml classes 2) Utility classes should not be pulled into auxilary bundles such as security (otherwise if app needs only utility class then it has to download extra files) 3) We should not put awt classes into swing bundles because they can be needed for pure AWT applications 4) Language specific resource files can be moved to separate bundles and downloaded if lang support is needed 5) Some libraries, such as dcpr.dll can be moved to separate bundles. These and some other ideas help to reduuce download footprint by 300-1100k depending on application.