xml-dev - Re: Parse Error Not Thrown When Expected

[John Cowan <jcowan@reutershealth.com>]

Laura Neitzel wrote:
> 
> The Xerces Validating SAX Parser is throwing a parse error in an unexpected
> place. Can someone tell me if this a bug or if this is how most parsers are
> intended to work?

There is no model for when validity errors are guaranteed to be fired.
A parser is free to fire them when it detects them, or even to save them
up to the end of the document and fire them all at once.  (Indeed, validity
errors like undefined ID *can't* be detected until the end.)

> The problem occurs when someone sends a document that violates the dtd rule.

I suggest switching from a SAX to a DOM model.  You can use my DOMParser
(http://www.ccil.org/~cowan/XML) to walk the DOM tree after it's generated.

-- 

Schlingt dreifach einen Kreis um dies! || John Cowan <jcowan@reutershealth.com>
Schliesst euer Aug vor heiliger Schau,  || http://www.reutershealth.com
Denn er genoss vom Honig-Tau,           || http://www.ccil.org/~cowan
Und trank die Milch vom Paradies.            -- Coleridge (tr. Politzer)

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************