logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Deboy" <sde...@comotivsystems.com>
Subject RE: Joran not reporting config errors
Date Mon, 29 Nov 2004 23:22:32 GMT
Are you suggesting we leave things as-is?

I think this will break most existing xml-based configurations (assuming that folks based
their config on one in the 'examples' directory):

At the very least I'd hope we could get Joran to report the error instead of silently swallowing
it.  Is that possible?  (maybe with a message in the console if they get an ILL_FORMED that
this could be due to the declaration?)

-----Original Message-----
From:	Ceki Gülcü [mailto:ceki@qos.ch]
Sent:	Mon 11/29/2004 3:16 PM
To:	Log4J Developers List
Subject:	RE: Joran not reporting config errors

In the case of DOMConfigurator we could fix it by changing the system
id to dummy://log4j.dtd at runtime. However, in the case of Joran we
can't set the system id and later complain to the user that we don't
want it.

Lacking a good and clean solution, the best approach I can think is to
assume that the XML file will have no system id. If we try to be 100%
compatible with existing XML files, then for those using Xerces or JDK
1.5, things will work whereas for those using JDK 1.4 things will
fail. Note that even under JDK 1.4, things will seem to work properly
if you use Ant.

My point is that these occasional hence inexplicable errors would
badly confuse the user. (Hard but immediate failures are 1000x better
than occasional failures.)

At 11:58 PM 11/29/2004, you wrote:

>The problem can be traced back to the different way Xerces and Crinson
>treat the URL of the system ID. In xerces writing
>   <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
>is acceptable whereas Crimson barks with "log4j.dtd invalid URL"

Ceki Gülcü

  The complete log4j manual:  http://qos.ch/eclm
  Professional log4j support: http://qos.ch/log4jSupport  

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message