« Return to Thread: Why our current logging approach will never work in Jetty

Re: Why our current logging approach will never work in Jetty

by Martin Desruisseaux-2 :: Rate this Message:

Reply to Author | View in Thread

Saul Farber a écrit :
> In the end, our CommonsLogger  will redirect to log4j, but will wind up
> answering the 'Logger.isLoggable()' question based on the reading of a
> config file (a bastardized log4j.properties use right now...but maybe
> something else in the future?)  Right?

In the CommonLogger (or Log4JLogger, or SLF4JLogger, or whatever) proposal, the
Logger.isLoggable() call would be redirected straight to commons-logging, or
Log4J, etc. We will not use the Java logging mechanism anymore, so there is no
need for configuration. The Log4J configuration would be the only one that matter.

        Martin

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@...
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

 « Return to Thread: Why our current logging approach will never work in Jetty