[jboss-jira] [JBoss JIRA] Updated: (JBDEPLOY-40) Allow subdeployment classloaders to become top level classloaders

[ http://jira.jboss.com/jira/browse/JBDEPLOY-40?page=all ] Adrian Brock updated JBDEPLOY-40: --------------------------------- Summary: Allow subdeployment classloaders to become top level classloaders (was: Add warnings about "spurious" subdeployment classloaders) Affects Version/s: JBDEPLOY-2.0.0.Beta15 (was: JBDEPLOY-2.0.0.Beta13) Description: 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. was: 1) People can accidently create subdeployment classloaders if they add jboss-classloading.xml to their META-INF of a subdeployment 2) If people do this deliberately and specify a classloading domain, the domain is ignored since the domain has to be controlled to have a parent of the main deployment classloader We should issue warnings at least for point (2). We could also issue a warning for point (1) when it is not a web-app since that is the intended use case. -- 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