For Tomcat I see there are two/three different paths that can lead us to rewriting the web.xml The class TomcatServiceEndpointPublisher starts a scanning thread to periodicaly check the JBossWS deploy folder, if a new archive is found this will cause the archive to be processed and the web.xml to be rewritten. I cant get JBossWS to deploy to Tomcat at the moment to test this out but as the scanner thread is already running within Tomcat shouldn't it already have a classloader? The second/third parth is when the deployer is called from the testsuite or when it is called from the command line, in this scenario the only classloader we have is the system classloader. This classloader should still have the JBossWS classes on the classpath. The only time we really need the classloader is to load the classes of the endpoints to check if the class is annotated with @WebService. What else do you see us needing available on the classpath? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978621#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...