Lists Home |
Date Index |
Elliotte Rusty Harold <firstname.lastname@example.org> writes:
> At 9:24 AM +0000 2/24/04, Michael Kay wrote:
> >On the subject of error handling, one of my biggest hassles in making
> >Saxon portable across different XML parsers has been differences in the
> >way they handle an exception thrown by a callback such as startElement.
> >They vary in whether or not such an exception is notified to the
> >ErrorHandler, and they vary in whether it re-emerges intact as an
> >exception thrown by the parse() method or whether it gets wrapped in
> >some other exception. The specs, of course, are very unspecific on such
> That's a tricky one, and one I'm not yet testing for. My reading of
> the spec is that such exceptions should not be reported to the
> ErrorHandler. The ErrorHandler is only for the use of the parser. And
> if the client app wants its exceptions to show up in the errror
> handler it can always call those methods directly.
How about if the "client app" is a SAXFilter? Then it's both a client
and a parser.
Elections only count as free and trials as fair if you can lose money
betting on the outcome.