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=35947>. 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=35947 Summary: DOMConfigurator reports XML validation problems as LogLog.error Product: Log4j Version: 1.2 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Configurator AssignedTo: log4j-dev@logging.apache.org ReportedBy: [EMAIL PROTECTED] In http://marc.theaimsgroup.com/?l=log4j-dev&m=112263727902752&w=2, A_Wieminer was quoted as saying: I have read from tomcat site, that if you use Log4j as a logging implementation you _must_ use .properties format. Its something to do with how webapp-level logging is configured and xml format incompatibilities. It is supposed to be fixed in later Log4j versions. The supposed problem was due to log4j.dtd specifying that the name attribute of a logger element be an ID (overly strict), Tomcat using logger names with characters prohibited by the XML ID type, and log4j reporting that as an error though the message does not adversely affect the configuration. The "fix" is the change to change LogLog.error to LogLog.warn and to tweak the wording to indicate that a validation failure (or other call to ErrorHander.error) is a "Continuable parsing error..." where a well-formedness error is a "Fatal parsing error...". log4j 1.2.12 candidate. -- 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]
