OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Parse Error Not Thrown When Expected

[ Lists Home | Date Index | Thread Index ]
  • From: John Cowan <jcowan@reutershealth.com>
  • To: Laura Neitzel <laura.neitzel@moai.com>
  • Date: Tue, 16 May 2000 17:29:53 -0400

Laura Neitzel wrote:

> I'm sorry, i must not have explained the problem well enough. I realize that
> SAX is event based and I believe that the error HAS occured when it reaches
> the end of teh element in question (the "Add" element). I just assumed that
> the parser would perform the validation BEFORE it fires teh event, not
> after.

I'm not clear on when you see the error. Is it when the offending second
element is seen, or when the container element is closed?  Either is a plausible
implementation strategy.  Expecting an error to be fired *before* the
previous element is ended is probably too much to ask.

A possibility: create the object in memory when you see the initial
endElement, check for validity when you see the container's endElement.


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/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS