Thanks for the suggestion, Glen, but this didn't appear to make any difference.
- Dennis On 02/11/2012 10:38 AM, Glen Mazza wrote: > Hi Dennis, Colm is the best one to answer, but I think the dependency > listed here: > https://github.com/Talend/tsf/blob/master/examples/jaxws-ws-secpol/service/pom.xml > at lines 78-83 is what will cause the WSS4J logging to activate. > Unfortunately there may be more moving parts involved, but that's all > I'm aware of. > > HTH, > Glen > > On 02/10/2012 04:28 PM, Dennis Sosnoski wrote: >> I'm trying to investigate a security problem. I'd like to turn on the >> wss4j logging so I can see what's happening internally, but using the >> standard log4j.properties file in the classpath doesn't seem to have >> any effect. Anyone know how I can control wss4j logging? >> >> I've also tried to switch CXF logging to use log4j as described here >> http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging-UsingLog4jInsteadofjava.util.logging >> but can't seem to make that work, either - the logging.properties >> file still seems to control the logging levels, and the output looks >> the same. >> >> Thanks for any suggestions, >> >> - Dennis >> > >
