• To: <xml-dev@l...>
• Subject: SAX and endDocument
• From: "Jeff Rafter" <lists@j...>
• Date: Sat, 20 Dec 2003 17:54:27 -0800

I was working with Xerces-J this weekend and encountered what I thought was
a
major bug-- however upon rereading the SAX API docs I suspect I may be
mistaken. For some reason I was under the impression that the endDocument
function was guaranteed-- meaning, that even in an exceptional circumstance
endDocument would be called. This allowed a guaranteed place (expeccially in
the case of filters) to do cleanup after a parse.

This is definitely the case for AElfred2, but the API docs are not crystal
clear on the subject (though I thought they used to be).  With AElfred2,
even in the case of a user generated exception the endDocument handler will
be called. In Xerces if an exception occurs it stops the process completely
omitting the endDocument call.

Can anyone clarify?

P.S. I tried to post this to sax-devel but it keeps rejecting me...

Jeff Rafter

• Follow-Ups:
  • Re: SAX and endDocument
    • From: "Karl Waclawek" <karl@w...>

• Prev by Date: Re: repercussions
• Next by Date: Re: SAX and endDocument
• Previous by thread: RE: repercussions
• Next by thread: Re: SAX and endDocument
• Index(es):
  • Date
  • Thread