[PATCH 0/2] Class- and class loader-local storage (Bug ID #6493635)

Bob Lee openjdk at crazybob.org
Fri Feb 27 20:59:25 UTC 2009

On Fri, Feb 27, 2009 at 12:48 PM, David M. Lloyd <david.lloyd at redhat.com> wrote:
> I don't think you understood what I wrote

I understood. I just think you're trying to solve a problem that no
one really has. 99% of the time, the problem is with a class from a
parent class loader keeping a strong reference to a class in a child
class loader.

If a class in a child class loader wants to keep a reference to a
class in a parent class loader, it can just do so directly--no need
for a weak reference.

It sounds to me like you want to support both cases at once, but I
don't think anyone really has this problem. At least, I've never seen
it. If they do, they should:

 a) redesign their code, or
 b) keep two maps, one for classes in child loaders (which need weak
refs), and one for classes in parent loaders (which don't)


More information about the core-libs-dev mailing list