logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gulcu <c...@qos.ch>
Subject Re: Separating Configuration
Date Thu, 05 Mar 2009 17:39:55 GMT
Hello,

Given that log4j is not designed for access logging, are you really
able to do access logging with log4j?

Chance Yeoman wrote:

 > I am working on a log4j implementation of the http request logger for
 > Jetty 6.1.7 and I had a question about the best practice for
 > separating logger configurations and hierarchies.  I would like to
 > line configuration up with current Jetty config as much as possible.
 > This would mean one default logger configured from a single config
 > file and the ability to create any number of new loggers on a context
 > basis that could be configured from their own files.  What's the best
 > way to keep these configurations separate and local to the server's
 > http request logging mechanism?  Should I create a LoggerFactory that
 > maintains it's own LoggerRepository just for the request loggers?

-- 
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


Mime
View raw message