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 2003/11/25 16:44:15 UTC
DO NOT REPLY [Bug 24973] -
chopping off data in characters method
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=24973>.
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=24973
chopping off data in characters method
mrglavas@ca.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From mrglavas@ca.ibm.com 2003-11-25 15:44 -------
This isn't a bug. SAX parsers are free to split character data [1] into as any
much chunks as they please, and they can split the text at whatever boundaries
they want. In order to handle this properly, your handler needs to accumulate
the text returned in each call until you recieve a callback that isn't
characters. We have an FAQ [2] on this since this seems to be a common
misunderstanding about how the characters callback of SAX works.
[1] http://www.saxproject.org/apidoc/org/xml/sax/ContentHandler.html#characters
(char[],%20int,%20int)
[2] http://xml.apache.org/xerces2-j/faq-general.html#faq-8
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org