openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Re: PCRegistry ClassLoader memory leak
Date Tue, 17 Jul 2007 04:15:32 GMT

On Jul 16, 2007, at 7:48 PM, Kevan Miller wrote:

> On Jul 16, 2007, at 10:26 PM, Pinaki Poddar wrote:
>> Just to clarify:
>> I meant it should be the loader that loaded Person.class where  
>> Person is
>> the persistence capable class, *not*
>> org.apache.openjpa.enhance.PersistenceCapable.class.getClassLoader().
>> But testing in multi-classloader environment is required to  
>> validate any
>> changes of this nature.
> Yes, that's how I interpreted your statement. My point is that if  
> SSN is a field of Person, the ClassLoader of SSN is not necessarily  
> the ClassLoader for Person. I'd be concerned that the Person  
> ClassLoader can't load SSN. In that case, your technique wouldn't  
> work...

Just to clarify, if SSN is the type of a field of Person, the  
ClassLoader of Person.class must be able to load SSN (either itself  
or via a parent ClassLoader) or you will have a linkage error while  
loading Person.


> Either way, would definitely require testing...
> --kevan

Craig Russell
Architect, Sun Java Enterprise System
408 276-5638
P.S. A good JDO? O, Gasp!

View raw message