"flavia.rainone(a)jboss.com" wrote : I was wondering is there is any way of identifying that specific type of scenario. If I could do that, I would generate the "bootstrap" CP only for "non-deployment" modules. This would avoid the problem in the scenario I described above without breaking testNonDeploymentModule. Actually, this is not what I want to do. This kind of fix would be useless, because, AFAIK, I could create the same ear scenario I described before using an beans.xml file. In that case, the "war" corresponding modules wouldn't be filtered out of JBossClDelegatingCPFactory.registerBootstrapLoaders, and the bug would occur again. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266507#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...