"kabir.khan(a)jboss.com" wrote : | Basically, it needs to be able to understand that the war entries should be part of a sub domain with their own class pool. I only started using JBossWebMetaData locally today to figure out whether the sub unit is a jar or not, so please ignore the talk about that. isAttachmentPresent(String name) should fix that for me. | ... | I want to know if we are using j2seClassLoadingCompilance or not, to be able to construct the new ScopedClassPools. Ok, this should be defined in the org.jboss.deployers.structure.spi.classloading.ClassLoaderMetaData, but I need to check that its correct. There is a bit of a disconnect between the war class loading deployer still having these settings, a jboss-web.xml having these settings for the legacy LoaderRepository, and the war deployers also trying to use their defaults. Once we have the org.jboss.deployers.structure.spi.classloading.ClassLoaderMetaData consistently defining the class loader for a deployment unit, it seems that you should not care about wars specifically. The ScopedClassPools should be driven off the unit ClassLoaderMetaData.isJ2seClassLoadingCompliance() setting regardless of the deployment unit type. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126318#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...