• From: John Cowan <jcowan@r...>
• To: Laura Neitzel <laura.neitzel@m...>
• 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@r...>
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@x...&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************

• References:
  • RE: Parse Error Not Thrown When Expected
    • From: Laura Neitzel <laura.neitzel@m...>

• Prev by Date: RE: Parse Error Not Thrown When Expected
• Next by Date: Re: Syntax and semantics
• Previous by thread: RE: Parse Error Not Thrown When Expected
• Next by thread: RE: Parse Error Not Thrown When Expected
• Index(es):
  • Date
  • Thread