logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 47772] Enable different Log4J per application
Date Mon, 31 Aug 2009 16:29:27 GMT

--- Comment #2 from Jacob Kjome <hoju@visi.com> 2009-08-31 09:29:24 PDT ---
This is already supported.  Read the documentation and search the list and wiki
[1] for the "Logger Repository Selector" concept.

Granted, there are issues with this.  If you use static loggers, you will find
that a given statically defined logger's configuration will be tied to the
first configured repository (probably the default one) and won't change with
changes to an app's logger repository configuration.  As such, you must use
instance loggers.

I can guarantee that no alternate, more robust, per/application logging scheme
will be implemented in Log4j-1.2.x.  You might look to get involved with
Log4j-2.x development (not that it's really ongoing ATM) or look to see if
maybe Logback [2] has such a feature (not saying it does, just something to
check out).

There is a Jira site for Log4j-2.x feature requests [3], which I suggest you
move this request to if you want to see it worked on (assuming Log4j-2.x work
actually begins).  If you do so, make sure to close this one.  If you don't
close this one, it will probably be marked as WONTFIX eventually.

[1] http://wiki.apache.org/logging-log4j/AppContainerLogging
[2] http://logback.qos.ch/manual/loggingSeparation.html
[3] https://issues.apache.org/jira/browse/LOG4J2


Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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

View raw message