[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: endDocument/fatalError warning

• To: Dennis Sosnoski <dms@s...>
• Subject: Re: endDocument/fatalError warning
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Wed, 10 Mar 2004 18:51:30 -0500
• Cc: David Megginson <dmeggin@a...>,XML Developers List <xml-dev@l...>,"SAX Developers' List" <sax-devel@l...>
• In-reply-to: <404F9CBA.4000501@s...>
• References: <40488A7C.90003@a...><p0601020ebc754043f412@[192.168.254.4]> <404F9CBA.4000501@s...>

At 2:54 PM -0800 3/10/04, Dennis Sosnoski wrote:

>I don't understand your logic in this, Elliotte. AFAIKS this method 
>will *never* be called after the parser has thrown an exception, 
>only before. I suppose if you want this to be completely correct it 
>could say something like "...about whether endDocument() will or 
>will not be invoked after the parser has reported a fatalError() (if 
>an ErrorHandler is used) and before the parser throws an exception." 
>That seems likely to confuse people more than the wording used by 
>David, though.

It will be called after the parser has reported a fatal error though, 
and we should really remove the but about the exception completely.
-- 

   Elliotte Rusty Harold
   elharo@m...
   Effective XML (Addison-Wesley, 2003)
   http://www.cafeconleche.org/books/effectivexml
   http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA

• References:
  • SAX/Java Proposed Changes
    • From: David Megginson <dmeggin@a...>
  • endDocument/fatalError warning
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: endDocument/fatalError warning
    • From: Dennis Sosnoski <dms@s...>

• Prev by Date: Re: endDocument/fatalError warning
• Next by Date: Re: GenX and attribute QNames
• Previous by thread: Re: endDocument/fatalError warning
• Next by thread: Locator2
• Index(es):
  • Date
  • Thread