The documentation you're referring to is for JBossWS 3.x.
For JBossWS 4.x / JBoss AS 7.x, please refer to
In particular, given this topic was not fully covered yet in the doc, I've just added the following:
One way to achieve the same in JBoss AS7 is to use the "LoggingInInterceptor" and "LoggingOutInterceptor" On server side or on Client side .
/* Following part of code is needed for client side Logging of Soap request/response */
/* We need to make sure that we place the "log4j.properties" file inside clients classpath */
Client client = ClientProxy.getClient(port);
On The Ser\ver Side For CXF SOAP Message Logging we can use the following System Property:
<system-properties> <property name="org.apache.cxf.logging.enabled" value="true"/> </system-properties>
You can use a proxy or if not possible (https) you can set this system-property
to enable the dump of any jaxws-soap-network traffic. Google for it to find more details.
In Jboss AS 7.1 , in the configuration/standalone-full.xml (or which you use ) , you can add this
And enable trace on console / file where needed. Also packages as org or javax should be set to warn level to avoid excessive logging