I had similar issue few days back, and added JVM argument -Dlog4j.configuration=my/log.properites to my websphere JVM container; This created visibility to org.apache.ws.* package under websphere trace and logging configuration. I then bumped traced level for these security packages from WAS admin console and could see all logs spit into my trace file.
And yes, adding log4j.properties to classpath and enabling logging/levels did not produce log output for me either. -- View this message in context: http://cxf.547215.n5.nabble.com/wss4j-logging-in-CXF-tp5473826p5474017.html Sent from the cxf-user mailing list archive at Nabble.com.
