RE: v. 1.2.0: When warning occurs, SAXParseException has always t he parsed XML doc's system id.

[Dean Roddey <dr...@portal.com>]

Those checks cannot be done until the whole DTD has been parsed, since until
we have passed the end of the DTD, we have to assume that the definition of
that element might still be in the pipeline. So the consistency checks of
that sort, which must be done post-DTD parse will show up in the context of
the main document from which the DTD was referenced.

--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
droddey@portal.com



-----Original Message-----
From: Pawel Hubczak [mailto:P.Hubczak@ost.com.pl]
Sent: Friday, December 22, 2000 2:22 AM
To: Xerces Mailing List
Subject: v. 1.2.0: When warning occurs, SAXParseException has always the
parsed XML doc's system id.


Hi

I am using v. 1.2.0.
When a warning is raised, e.g. in an external DTD, when there is a reference
in content model to an element that is not defined,
the SAXParseException::getSystemId (received by my Error Handler class)
always returns the parsed XML document system id. Shouldn't this be the
external entity system id where the exception occurred?

Regards,
Pawel



---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org