DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305 Use thread context class loader for loading Summary: Use thread context class loader for loading Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Configurator AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The current use of Class.forName in classes like org.apache.log4j.xml.DOMConfigurator restrict flexibility of how appenders, filters, etc. may be loaded into the VM. When used in an application server this forces all dynamcially loaded objects to be in the same classpath namespace that loaded the log4j.jar. There is no drawback to using the thread context class loader instance of Class.forName and there are many advantages. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
