You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2002/05/23 17:12:55 UTC
DO NOT REPLY [Bug 9350] -
SAX parser calls characters() with wrong buffer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9350>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9350
SAX parser calls characters() with wrong buffer
gmarcy@us.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From gmarcy@us.ibm.com 2002-05-23 15:12 -------
SAX is free to split your character data up into multiple calls to the
characters() method. SAX is also free to call startElement() when it has
successfully parsed the start tag and does not need to wait until/if it
sees a matching end tag. These are both pragmatic decisions given that a
perfectly good XML document could be a start tag followed by megabytes of
character data followed by the matching end tag. It would be unreasonable
for SAX to force implementations to buffer all of that data or for it to
force applications to wait until the entire document was check for balanced
tags before any data was available.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org