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 15:42:24 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

craig.mcclanahan@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From craig.mcclanahan@sun.com  2004-08-09 15:42 -------
Thanks for the further explanation -- it makes the correct resolution clear.

> This logger is not configuring Log4j,  it is passing the name
> of the configuration file and an option check interval to Log4j.
> What Log4j does with the information is outside the scope of the logger.

Regardless of the attempt at creative terminology :-), this is an attempt to
play the role of managing configuration of the underlying logging
implementation.  That is not what Commons-Logging is for.  You should use the
standard facilities of Log4J for that purpose.

> The default behavior of Log4j is controlled, in part, by system
> properties.  In a servlet container environment, i.e. Tomcat,
> their are many application but only 1 set of system properties.

I am not a Log4J expert, but my understanding is that the latter sentence is
definitely not true (the Log4J docco and user list would have more information
-- you could, for example, write a ServletContextListener containing the guts of
your setupLog4J() method, without changing anything about Commons Logging).

Regardless, however, whether you call this "configuration" or "setup" it should
be done directly using the APIs that Log4J provides for that purpose.  Commons
Logging is about abstracting the *use* of the loggers, not their setup.

---------------------------------------------------------------------
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