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=4244>. 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=4244 Expression02 seems to fail in incremental mode ------- Additional Comments From [EMAIL PROTECTED] 2002-02-05 22:50 ------- I suspect what's happening is that the "magic" construction sequence we were given for an incremental SAX parser is not setting all the same flags we're setting on the normal parser. Specifically, I suspect it isn't reading the internal subset, and thus isn't creating the unparsed-entity information. (Which is one of many reasons I want Xerces to re-create an official SAX-level incremental parsing control, as they did in the prototypes. Unfortuately they have been unwilling to consider supporting that option. Grumble.) BTW, the reason the problem doesn't arise for SAX or DOM flavors is that if you pass in a SAX stream we implement incrementality via a "throttling" filter, and if you pass in a DOM we always build the DTM incrementally whether you tell us to or not. Only when reading from a file do we create our own SAX parsers, and that's the only time when we have the opportunity to try to leverage Xerces' incremental features. So a workaround until we get this settled is indeed to create your own instance of Xerces and pass us the SAXSource, and let us throttle that down to speed. It won't be as elegant or efficient. But it will do the job.
