[
https://jira.jboss.org/jira/browse/JBCL-125?page=com.atlassian.jira.plugi...
]
Adrian Brock commented on JBCL-125:
-----------------------------------
I'm going to fix this by making the wanted behaviour explicit in the metadata.
i.e. there will be a new flag in jboss-classloading.xml
<top-level-classloader>true</top-level-classloader>
which will create a true top-level classloader with your specified domain
rather than a sub-deployment classloader with the top-level classloader as parent.
Cannot control the domain name for a classloader in a subdeployment
-------------------------------------------------------------------
Key: JBCL-125
URL:
https://jira.jboss.org/jira/browse/JBCL-125
Project: JBoss ClassLoader
Issue Type: Bug
Components: MetaData
Reporter: Adrian Brock
Assignee: Adrian Brock
Fix For: JBossCL.2.0.8.GA
As documented in FAQ, one of the ways to share classes between wars and other
deployments
is to explictly put them in a domain, e.g. the DefaultDomain
http://www.jboss.org/community/wiki/useJBossWebClassLoaderinJBoss5
However when the war is a subdeployment the AbstractClassLoaderDescribeDeployer is
ignoring
the domain specified in the jboss-classloading.xml and using the deployment's unit
name as the domain.
This is only true if you don't specify a parent-domain for the subdeployment's
classloader.
But if you want to put the classloader in the "DefaultDomain" you can't
specify the parent since it doesn't have one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira