This content has been marked as final.
Show 5 replies
-
1. Re: Context ClassLoader - Deployers
starksm64 Jan 22, 2008 6:49 PM (in response to adrian.brock)I agree on using the deployer class loader.
-
2. Re: Context ClassLoader - Deployers
adrian.brock Jan 24, 2008 7:27 PM (in response to adrian.brock) -
3. Re: Context ClassLoader - Deployers
adrian.brock Jan 24, 2008 7:32 PM (in response to adrian.brock)"adrian@jboss.org" wrote:
Jira Issue http://jira.jboss.com/jira/browse/JBMICROCONT-231
This has been done.
The only issue is whether we should clone the BeanMetaData before
modifying it's ClassLoaderMetaData.
For now I've chosen not to do that (Ales, did you test the cloning works properly?)
instead, the modified metadata is removed at undeployment to avoid memory leaks
on the classloader. -
4. Re: Context ClassLoader - Deployers
adrian.brock Jan 24, 2008 7:51 PM (in response to adrian.brock)Just to make it clear with this change and http://jira.jboss.com/jira/browse/JBMICROCONT-230
What will happen now by default is that a my-deployer-beans.xml
will get its own classloader (it's a deployment).
The deployer in that xml will install into the MainDeployer which will remember the
classloader (its the context classloader) for invoking un/deploy() of the deployer.
This is more intuitive than using the bootstrap classloader or some random
context classloader of an RMI/HTTP thread when invoking deployers. -
5. Re: Context ClassLoader - Deployers
alesj Jan 25, 2008 10:16 AM (in response to adrian.brock)"adrian@jboss.org" wrote:
For now I've chosen not to do that (Ales, did you test the cloning works properly?)
This should be done as part of http://jira.jboss.com/jira/browse/JBMICROCONT-28.
Where I'm still waiting for the introduction of UUID for the name, to get this fully implemented.
- http://www.jboss.org/index.html?module=bb&op=viewtopic&t=101320&start=20
So there is currently no cloning, hence no testing. :-)