I think that this is a SAX convention, which is why the suppression was
added. If the SAX spec says that such events won't show up, we can't send
them because it could seriously freak out applications written to the SAX
spec.
We could argue that the advanced handler, since its already outside of the
SAX spec could be invoked no matter what, and the suppression only applied
to the SAX specific handler I guess. But, if you are already outside of the
SAX specification anyway, and the advanced handler is proprietary to the
Xerces parser, you could just as easily use the internal event interface and
get better performance and be sure that you are getting all of the info set
available.
--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-----Original Message-----
From: Chris Hill [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 26, 2001 3:18 PM
To: [EMAIL PROTECTED]
Subject: comments outside root
My advanced handler (XMLDocumentHandler) wasn't receiving docComment events
for comments outside the root element, so I took a look at
SAXParser::docComment, and it is intentionally suppressing the events. Is
there any particular reason that comments outside the root are
suppressed? Processing instructions are permitted, why not comments?
Looking in the CVS log I see that this behavior was changed then changed
back in SAXParser.cpp 1.12 and 1.13. Perhaps comments slipped through the
cracks? In the mail archives, I found a fragment of a conversation about
this. I don't think comments should be suppressed.
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
