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 [EMAIL PROTECTED] 2004-08-09 13:08 ------- 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. This logger is a wrapper to the existing Log4jLogger. It only provides constructors that get the file and interval value from JNDI and pass them to Log4j. It the JNDI configuration is missing, then the "default" behavior is defined by Log4j. I am aware of the previous "discussion" around the Log4jLogger when it was defining appenders instead of allowing the default behavior of Log4j. I do not believe this implementation crosses that line. As to you questions: 1) Why does this belong in Commons-logging, instead of Log4j? 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. Thus you can not configure th application webapp_a to use webappA_log4j.xml and webapp_b to use webapppB_log4j.xml. This logger is only passing the name of the configuration file and an optional check interval to Log4j. 2) 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? The logger is only passing the name of the configuration file and an optional check interval to Log4j when they exist. It is not affecting the default behavior of Log4j. This the behavior logger "foo.bar.baz" is not affected by this logger. The behavior is defined and maintained by Log4j. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
