[jboss-jira] [JBoss JIRA] Commented: (JBDEPLOY-40) Allow subdeployment classloaders to become top level classloaders
[ http://jira.jboss.com/jira/browse/JBDEPLOY-40?page=comments#action_12414802 ]
Adrian Brock commented on JBDEPLOY-40:
--------------------------------------
I've made this possible depending upon whether the user specifies the parentDomain or
not
in the classloading metadata.
If the parentDomain is specified then the subdeployment classloader becomes a top level
classloader,
otherwise a synthetic domain is constructed based on the deployment's main
classloader.
I also added some DEBUG logging to say which is being used.
Allow subdeployment classloaders to become top level classloaders
-----------------------------------------------------------------
Key: JBDEPLOY-40
URL: http://jira.jboss.com/jira/browse/JBDEPLOY-40
Project: JBoss Deployers
Issue Type: Feature Request
Components: classloading
Affects Versions: JBDEPLOY-2.0.0.Beta15
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBDEPLOY-2.0.0.CR1
Add the ability for subdeployment classloaders to become "top level"
classloaders.
This reproduces some of the older classloading behaviour for webapps where
"UseJBossWebClassLoader" was true and the loader repository specified.
This allows the two subdeployments to share classes.
With the new subdeployment classloader for any time of deployment,
this would be useful generically.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira