Besides that, you can still manually add the logging beans providing a custom jbossws-cxf.xml file in your deployment, take a look at the jbossws-cxf samples to see where to put the file to make sure it's picked up.
Thanks for spotting the issue in the doc.
Actually, I have tried the above custom jbossws-cxf.xml file in the META-INF folder of my application's deployment, as described here: http://www.jboss.org/community/wiki/JBossWS-StackCXFUserGuide but it had no effect on message logging (the endpoint configuration works correctly).
However, I have found that if I put a cxf.xml file with the logging configuration in WEB-INF/classes in my deployed app, logging seems to work. It's a bit of an inelegant solution, but I'm using it as a workaround for now. [/url]
I've update the doc at http://www.jboss.org/community/wiki/JBossWS-StackCXFUserGuide#SOAP_Message_Logging. Basically, as you can get from the changes for JBWS-2765 and JBWS-2836, the doc there was out of date as the referred configuration file was not installed in recent jbossws-cxf versions.