I'm sorry, I'm failing to be very helpful. This will have to wait for someone with more understanding of this area to turn up.
On Wed, Dec 30, 2009 at 8:53 PM, conficio <[email protected]> wrote: > > > bimargulies wrote: >> >> 2.0.12 so old that all bets are off. >> > Well, as the relevant code has not changed up to 2.2.4, I'd be happy to know > the solution for any newer version. > > I have tested that > log4j.category.org.apache.cxf=ERROR > > does suppress the stack trace. But I don't know why I need to cast such a > wide net. Any ideas? > > By the way that code would be improved to not log a stacktrace at a warning > level, but rather a message and the stacktrace only at debug level. > -- > View this message in context: > http://old.nabble.com/cxf-stop-logging-stack-trace-for-false-authentication-in-2.0.12-tp26950197p26974446.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
