In ESB 4.x you can specify that a deployment be scoped by configuring this in deployment.xml: <jbossesb-deployment> | <depends>jboss.esb:test=server</depends> | <depends>jboss.esb.qa.junit.destination:service=Queue,name=esb_gateway_channel_versioned</depends> | <depends>jboss.esb.qa.junit.destination:service=Queue,name=esb_channel_versioned</depends> | <loader-repository> | org.jboss.soa.esb:loader=simple-scoped | <loader-repository-config> | java2ParentDelegaton=false | </loader-repository-config> | </loader-repository> | </jbossesb-deployment> In AS 5.x something similar can be done by adding a META-INF/jboss-classloading.xml file to a deployment. I'm guessing that our deployers should act upon a loader-repository element in deployment.xml and take care of this when a .esb archive is deployed into AS 5, and not force users to declare such a file? /Daniel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227536#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...