Until now I learned that LOGBACK can replace java.util.logging only for access logging until. It seems, only log4j can provide a full java.util.logging replacement. As LOGBACK can't replace JUL, I can't use LOGBACK to control WebApplicationLogging centrally, though I'm no longer sure that this might be a good idea, anyway. I learned to control the access log now, so I'm done with my question.
-- View this message in context: http://logback.10977.n7.nabble.com/How-to-control-WebApp-logging-by-Tomcat-control-files-tp13547p13554.html Sent from the Users mailing list archive at Nabble.com. _______________________________________________ Logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
