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=42172>. 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=42172 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2007-04-19 13:17 ------- You have every right to find it wrong if you like, and I perfectly understand the "issue", however what I am telling you is that this will not be fixed. As far as I am concerned, providing the logging framework with a webapp is possible, and can sometimes be useful, but reloading will cause problems. If you want to use reloading, you can either stop using log4j and use java.util.logging instead (as it is a one-per-JVM logging service, it is much more robust), or package your application differently (log4j and the commons-logging wrapper for log4j should be moved to a shared CL repository). Reopening this report is not going to change this. -- 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]
