avalon-phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <pe...@apache.org>
Subject Re: Cascading PolicyClassLoaders, a bug?
Date Thu, 21 Mar 2002 13:53:52 GMT

Redirecting this to the phoenix list...

I just made some changes tonight to fix this I think. Funnily enough it had a 
TODO right above it indicating that it should be fixed ;)

I haven't fully tested it and wont have a chance till Monday but all prelim 
tests seem to work. Could you try your application and see if it fixes your 

On Thu, 21 Mar 2002 01:02, Marcos Sanz/Denic wrote:
> Hi all,
> I have researched the problem that I mentioned yesterday and it seems to me
> to be a systematic flaw:
> Embeddor calls Deployer.
> Deploying first application: ClassLoaderManager creates first application's
> ClassLoader, setting as a parent the current thread's context ClassLoader
> (still the right parent). Deployer calls Kernel and Kernel calls
> Application.start(). Key point now:
> ThreadContext.setThreadContext(m_context.getThreadContext()) changes
> current thread's context ClassLoader to be the first applications's
> ClassLoader ("for calling visitors", it's ok).
> But now Deployer deploys the next application, and ClassLoaderManager
> creates second application's ClassLoader, setting as a parent the current
> thread's context ClassLoader, which is the wrong parent, since it is first
> application's ClassLoader.
> Third application would set as a parent the second application's
> ClassLoader and so on...
> Peter, Leo: is this a bug? Have I overseen something?
> Best regards,
> Marcos Sanz



"I would like to take you seriously but to do so would 
affront your intelligence" -William F. Buckley, JR

To unsubscribe, e-mail:   <mailto:avalon-phoenix-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-phoenix-dev-help@jakarta.apache.org>

View raw message