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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2005-02-09 02:27 ------- There is a fundamental misunderstanding here of the purpose and nature of commons-logging. It may be somewhat confused by the existence of the Log4jFactory. Note the following, from the Log4jFactory javadoc: * @deprecated Per discussion on COMMONS-DEV, the behind-the-scenes use * of this class as a proxy factory has been removed. For 1.0, you * can still request it directly if you wish, but it doesn't really * do anything useful, and will be removed in 1.1. Now, that aside, the Log4jFactory does NOT "initialize" or "manage" Log4j: feel free to review the source for Log4jFactory, it doesn't have anything to do with initializing Log4j. And neither should commons-logging. It's not designed to "manage" the logger impl. THAT task remains in your core application. Please note that commons- logging is NOT intended to make your *application* independent from a logger implementation, though you are welcome to use it's API's to minimize impact to your application if you choose to change logger implementations. JCL is designed to help make your *components* [not applications] independent from logger implementations. You wouldn't expect each individual component to try to start/stop your apps logger, and so you shouldn't expect commons- logging to do so either [weak analogy, if you have complaints, forget it..]. The *expected* behavior of your application/framework is as follows: app startup: - initialize logging implementation [Avalon, Log4j, Whatever] - JCL configured to use appropriate logging impl, possibly via commons-logging.properties file - initializes components & begins processing component at runtime: httpclient: component logs using JCL axis: component log using JCL other component(s): log using JCL app shutdown: - shutdown components [as needed] - shutdown logging [if needed] At NO time does JCL presume to *know* that your app is starting up or shutting down, it presume only that you want to use a specific logger impl, and presumes that your app runtime environment will supply the appropriate logger. Please also see the note I sent to the developers mailing list on this topic, it provides additional details on how your proposed "fix" will cause problems in other environs. -- 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]
