Bug 35947 - DOMConfigurator reports XML validation problems as LogLog.error
DOMConfigurator reports XML validation problems as LogLog.error
Status: RESOLVED FIXED
Product: Log4j
Classification: Unclassified
Component: Configurator
1.2
Other other
: P2 normal
: ---
Assigned To: log4j-dev
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2005-07-31 01:53 UTC by Curt Arnold
Modified: 2005-07-30 18:03 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Curt Arnold 2005-07-31 01:53:19 UTC
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.