JDK-6649414 : New plug-in continues to load Swing classes
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-01-11
  • Updated: 2010-09-08
  • Resolved: 2008-01-31
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 b11Fixed
Related Reports
Relates :  
###@###.### pointed out that the new Java Plug-In was still loading some Swing classes like javax.swing.JFrame in support of the ConsoleWindow, even if the Java Control Panel setting was to not show the Java Console. It was stated that the old Java Plug-In did not exhibit this behavior.

SUGGESTED FIX http://j2se.east.sun.com/deployment/www/webrevs/ccheung/1.6.0/6649414/webrev/

EVALUATION Investigation with ###@###.### showed that because the return type of the method sun.plugin.JavaRunTime.getJavaConsole() was ConsoleWindow, simply loading the JavaRunTime class was forcing ConsoleWindow and all of its superclasses to be loaded. This must have been true of the old plug-in as well, only because the old plug-in's tracing code was initialized later than in the new plug-in it was not apparent. Changing this method to return Object and doing explicit casts at the call sites solves the problem.