JDK-6824169 : Need to remove some AWT class dependencies
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6u14
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows
  • CPU: x86
  • Submitted: 2009-03-31
  • Updated: 2013-11-01
  • Resolved: 2009-04-21
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.
JDK 6 JDK 7
6u14 b05Fixed 7Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
There are some dependencies on some AWT classes that may impact on the startup performance. The list below explains some of the dependencies:

- the usages of the reflection API to access the private fields/methods

The usages may cause to load of some unexpected AWT classes. For example, the PopupMenu class (and some other classes) is a part of the method signatures of the Component class and the classes are loaded during the reflection API calls. For more information, please refer to the CR 6823296 (Class.getDeclaredMethod, getMethod, getDeclaredField, getField cause many classes to be loaded).

- the usages of the instanceof operator

The usages may cause to load of some unexpected AWT classes as well. For example, the GDIWindowSurfaceData class have some optional dependencies on the WFileDialogPeer, WPrintDialogPeer classes.

Comments
SUGGESTED FIX http://sa.sfbay.sun.com/projects/awt_data/6u14/6824169/
2009-04-13

EVALUATION Need to be fixed.
2009-04-09