Re: [xml-dev] SAX/Java Proposed Changes
Elliotte Rusty Harold <[email protected]> Mon, 8 Mar 2004 16:12:17 -0500
| Newsgroups | gmane.text.xml.sax.devel,gmane.text.xml.devel |
|---|---|
| Message-ID | <p06010215bc72919abd26@[192.168.254.4]> |
At 9:30 PM +0100 3/8/04, Jochen Wiedmann wrote: >Elliotte Rusty Harold wrote: > >> Then your code will break when used with some of today's parsers >>which do call endDocument() after a fatal error.. :-( > I'm not sure what this program is supposed to demonstrate. One of the conclusions I think we're reaching is that if a client supplied method such as startDocument() throws an exception, then endDocument (and fatalError()) are not called. endDocument() and fatalError() are for the use of the parser only. If the client chooses to prematurely abort processing by tossing an exception, then the client has the responsibility to clean up before doing so. The client can't do that so easily when the parser is choosing to end parsing. But maybe you were trying to say something else and I'm jusat not seeing it? -- Elliotte Rusty Harold [email protected] Effective XML (Addison-Wesley, 2003) http://www.cafeconleche.org/books/effectivexml http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ List: sax-devel, [email protected] See: http://www.saxproject.org/ https://lists.sourceforge.net/lists/listinfo/sax-devel