Re: Problem with Crimson parser

Ceki Gï¿½lcï¿½ Wed, 03 Sep 2003 10:30:01 -0700

Mark,

Can you please provide the XML file causing trouble?

The commit you mention is also available in 1.2.8. (that is why I asked if you were using 1.2.8.).

At 06:00 PM 9/2/2003 -0400, [EMAIL PROTECTED] wrote:

Hi,

I am having trouble parsing my config file with DOMConfigurator using Crimson. I have no problems with Xerces but when I use crimson I get the exception at the end of this message.

Somehow, Crimson is not able to find the dtd using the SYSTEM identifier log4j.dtd. I noticed there was a recent commit that added a class UtilLoggingEntityResolver.java with the following comment:
        // we change the system ID to a valid URI so that Crimson won't
        // complain. Indeed, "log4j.dtd" alone is not a valid URI which
        // causes Crimson to barf. The Log4jEntityResolver only cares
        // about the "log4j.dtd" ending.
Is there a work-around I can use for Crimson without having to use the latest CVS code? As an aside I don't think log4j.dtd is an invalid value for system identifier. I just looked in the W3C XML spec and it has an example with another such system identifier.


--
Ceki Gï¿½lcï¿½

     For log4j documentation consider "The complete log4j manual"
     ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp

     See you in November at ApacheCon US 2003 in Las Vegas.
     http://apachecon.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with Crimson parser

Reply via email to