Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of awhite@bea.com designates
 66.248.192.21 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <9565638.post@talk.nabble.com>
References: <9565638.post@talk.nabble.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F4610D0E-FBC2-4871-BBA8-1C6BE736E186@bea.com>
Content-Transfer-Encoding: 7bit
From: Abe White <awhite@bea.com>
Subject: Re: Shared classloader and subclasses
Date: Tue, 20 Mar 2007 11:14:24 -0500
To: open-jpa-dev@incubator.apache.org

> AFIACT, the problem is that the openjpa.enhance.PCRegistry class  
> uses static
> fields to store Meta information. When the second instance is  
> loaded, the
> PCRegistry has been initialized, but doesn't contain that instance's
> subclasses and an exception is thrown

The PCRegistry has to use static members because each persistent  
class registers itself with the registry in its static initializer.   
There is no way for a persistent class to access a specific registry  
instance when it is loaded into the JVM.

I don't think the proposed patch is viable, because there are cases  
where we lazily-load metadata, and we don't want to leave out  
subclasses just because we haven't parsed their metadata yet.  What  
is the exception you're seeing?
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.