Web services debug logging is causing the classloader to be switched.

Currently the web services stack does not correctly set the classloader for web services deployments when deployed as part of an ear with an issolated classloader (see JBWS-941). However debug logging in the web services code is incorectly causing the deployment to work!

In the class 'org.jboss.ws.server.ServiceEndpoint' there is a method called 'postProcessResponse', this method contains some logging wrapped with a 'log.isDebugEnabled': -

// debug the outgoing message
if(log.isDebugEnabled())

{ resMessage.saveChanges(); SOAPEnvelope soapEnv = resMessage.getSOAPPart().getEnvelope(); String envStr = DOMWriter.printNode(soapEnv, true); log.debug("Outgoing SOAPMessage\n" + envStr); }

If this logging is remove the ClassNotFoundException is thrown regardless of the log4j configuration.

The ClassNotFoundException is good and shows that the classloader has not been switched.

I will attach a deployment that can be used to reproduce this.