anonymous wrote : | On the first port of the war deployer, jbossweb didn't have a mechanism to accept a class loader so it was commented out. It should be creating a scoped class loader by default though, but its probably still an implementation detail of the webcontainer. It does need to be pulled out so its available at the DeploymentUnit level. I assume that is what you are looking for? | Ah I see. Yes, the issue is that the WS deployer has to inspect every war (WS or not) by loading all servlet classes (and related WS classes if it is in fact a WS deployment). If the DeploymentUnit CL is not isolated, there is the possibility of a conflict with multiple deployments. That said, fixing EAR isolation will resolve the WS TCK issues, since they separate the client and server side components in individual EARs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029486#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...