This is only on startup of the server or for any war deployment? The webservice deployer will not be a sar that integrates via jmx events in jboss5.
I'm still having problems with classloading. I moved the annotation processing for WARs in the start() method of the WebappLoader to make absolutely sure that the classloader is initialized and ready to go before processing annotations.
I'm still getting the same exact problem at boot time of not being able to discover a WS class that is deployed in a JAR the same level as the WAR (see above)
Is there any classloader procesing that happens after the WebappLoader has started?
It should be fully setup at that time. Is there a deployment in the testsuite that shows what you are trying to do?