ulrich, you may want to checkout these pages
https://github.com/grgrzybek/tomcat-slf4j-logback (an example implementation of using logback with tomcat for all logging) http://www.slf4j.org/legacy.html (some overview of how to use slf4j to support legacy logging interfaces) in short logback and slf4j can replace anything you might be using log4j for if you are using logback for access logging under tomcat you may also want to add the Remote IP Valve to your tomcat configuration if you are running behind a load balancer that provides X-Forwarded-For headers ________________________________________ From: Logback-user <[email protected]> on behalf of Ulrich <[email protected]> Sent: Monday, April 21, 2014 00:04 To: [email protected] Subject: Re: [logback-user] How to control WebApp logging by Tomcat control files 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 _______________________________________________ Logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
