It turns out,
you can get access to fields and methods in JDK classes declared as 'private' through reflection.
I don't recommend this and prefer not to use what I'm about to describe. In fact, I consider what I'm about to describe as an option of last resort.
Recently, I ran into
bug 6526376 which describes a memory leak in the JDK that impacts products that use java.io.File.deleteOnExit(). This method tracks the file that will be deleted in a statically defined Set in class...
Published on January 02, 2012 07:11