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:39 ------- Would note that Vedran has already discovered that Log4jFactory is NOT used [by default] with JCL, as his patch is placing a Log4J specific call to LogManager.release() into LogFactory, as opposed to Log4jFactory. As stated, for web-apps: The web-app OWNS the logging implementation, unless you have some understanding that your HOSTING environment is fronting JCL and a logger impl for you. In the first case, the web app is responsible for initializing and terminating the logger, as appropriate, for the context of the web-app. Your app may ALSO choose to use JCL. The benefits are: - if you elect to use a different logger impl [initialize & terminate as appropriate for THAT logger impl], then you won't have to change any other part of your web-app. - if your web-app is using OTHER components [many open-source components] and technologies that leverage JCL, then they will log as you would like them to, in the context of your web-app. In the second case, you might reasonably assume that the hosting environment should to "do what is right" to manage the logger impl [whatever that means].. but that falls outside the scope of JCL and this defect. -- 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]
