...I was wondering - is this a bug of the component that produces the
SAX events or the XMLByteStreamCompiler? I mean: now it's ok - but should we
silently ignore the problem?
Torsten, I don't understand your concerns. Isn't the fix simply about handling text nodes longer than 32 k? Ok, they shouldn't occur that often (it's half a novel :-) ), but it's possible.
....we duplicate events here and the thereby modify the SAX stream. Should be no problem.... but who knows ;)
with the patch:
characters(36k) -> event string 32k event string 4k
I guess it would be better to have it like this:
characters(36k) -> event string 32k string 4k
So what goes in comes out the same way.
According to the SAX spec, a single text node can be split in an sequence of consecutive character() events, and all SAX handling code should be written to take care of this.
So sending two events should really not be a problem.
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
