The last problem I'm seeing with pulling the war deployer class loader creation into the WarClassLoaderDeployer is a failure for a war in a scoped sar to see classes from the sar. The sar has a separate ClassLoaderDomain resulting from a scoped sar LoaderRepositoryConfig being mapped by the HackClassloaderMetaDataDeployer. I'm not seeing any interaction between the sar ClassLoaderDomain and the default ClassLoaderDomain that the war class loader is associated with. I guess the war class loader needs to be using the same ClassLoaderDomain as the sar. The problem is, its not available in the DeploymentUnit. Only the ClassLoader and ClassloaderMetaData is. Although the domain name is in the ClassloaderMetaData, I don't have access to the ClassLoaderSystem to lookup the domain without setting it. I do happen to have access to this because the WarClassLoaderDeployer needs it for other reasons, but we need to make it easier for subdeployments to build class loader in the correct domain. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123960#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...