When you want to run on Axis instead of JBossWS you need to undeploy jboss-ws4ee.sar. The last time I looked, Axis was holding static references to classloaders, which do not play well with the notion of LoaderRepositories and redeployment in general.
Thanks Thomas. That worked for me. Just ensuring that the WS4EE SAR isn't deployed allowed me to deploy my WAR (I don't even need the jboss-web.xml when I do this - all defaults seem to work out fine).
Can I assume that this WS4EE SAR is used only to deploy web services as per JSR-109 (aka the J2EE-way)? In other words, can I assume that if I just want to deploy Axis myself in my own WAR that I won't need the WS4EE SAR functionality for anything?
Correct, when you undeploy JBossWS will no longer have support for deployments J2EE compatible web service endpoints and clients.
Also make sure, you remove the jaxrpc related jars from $JBOSS_HOME/client and use the JWSDP client jars instead.