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=32662>. 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=32662 ------- Additional Comments From [EMAIL PROTECTED] 2005-02-09 02:51 ------- Hi Richard, Ok, I'll buy the argument that commons-logging should be viewed as an API to wrap "use" but not "configuration" of the underlying concrete log library In this case, things are a bit more confusing because commons-logging *does* implicitly manage log4j's initialisation: when the first log4j Log instance is instantiated (via the appropriate commons-logging wrapper class), this triggers log4j to scan for a config file, load it, and initialise itself. And as loggers are often created as static members of classes, it is rather tricky to ensure that app-specific log initialisation code has been run before the first commons-logging Log object triggers log4j's default initialisation. Sorry if a solution to that has been raised on the logging email thread that occurred recently; I tried to keep up with that but the volume just got too great.. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
