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" message.
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/eclm
Professional log4j support: http://qos.ch/log4jSupport
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
