[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Piccolo Java SAX parser and others in the wild?
Elliotte Rusty Harold <elharo@m...> 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 > >points. > > > > 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. Ari. -- Elections only count as free and trials as fair if you can lose money betting on the outcome.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|