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
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
