commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 30531] - Jndi configurable Log4j logger
Date Mon, 09 Aug 2004 04:54:38 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30531>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30531

Jndi configurable Log4j logger





------- Additional Comments From craig.mcclanahan@sun.com  2004-08-09 04:54 -------
This seems like a *very* useful enhancement for Log4J.  What I'm having a harder
time understanding is why it would belong in commons-logging -- where
configuration of the underlying logging system is *explicitly* out of scope?  No
matter how you might configure a (Log4J implemented) logger named "foo.bar.baz",
the commons-logging standard implementation will utilize it, with no special
behavior needed, right?

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


Mime
View raw message