Hi, Tried that approach, but now I have a problem in that the ESB is complaining about classes not being found. The jboss-classloading.xml is placed in the esb.deployer, so I assume that isolation is now causing the jbossesb.sar to not resolve classes that it previously referenced from the esb.deployer. So I assume to overcome this, I would need a jboss-classloading.xml in the jbossesb.sar? The jbossesb.sar has a deployment.xml but it does not have a dependency on the deployer - if it did, would this overcome the problem? or do all deployment units that depend upon the ESB need to have its own jboss-classloading.xml? i.e. any .esb distribution? The other problem with this approach is that it requires me to modify the ESB distribution. Is there no mechanism to just enable my sar to indicate that it wants to have only its own libs, and the jboss AS libs on its classpath? Regards Gary View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249415#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...