|
Quick Lists
|
|
Bug ID:
|
6810254
|
|
Votes
|
0
|
|
Synopsis
|
Lazily instantiate the shared secret access objects
|
|
Category
|
java:other
|
|
Reported Against
|
|
|
Release Fixed
|
7(b53)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
6798873
|
|
Submit Date
|
25-FEB-2009
|
|
Description
|
sun.misc.Java*Access objects are created at initialization time. They are only needed when certain API is used. They can be initialized lazily when needed.
These shared secret access customer provides a mechanism for calling implementation-private methods in another package while avoiding the primary disadvantage of using reflection for this purpose, namely the loss of compile-time checking.
Posted Date : 2009-02-25 23:51:30.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
Decouple class dependency for JDK7
Posted Date : 2009-02-26 00:00:54.0
The fix is to register the shutdown hooks only when needed so that java.io.Console and other implementation classes for deleteOnExit hooks and application hooks are not loaded unless they are needed.
JavaIODeleteOnExitAccess will be removed and the other shared secret access objects will remain to be set up during initialization.
Posted Date : 2009-03-12 17:20:07.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |