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=4912>. 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=4912 Incremental Processing blocks ------- Additional Comments From [EMAIL PROTECTED] 2001-11-16 07:15 ------- Important question: Are you passing a SAX stream from Xerces to Xalan, or are you letting us instantiate the parser? If the former, we have to use our IncrementalSAXSource_Filter code. The coroutine logic there _should_ be extremely robust against lockups... but it's possible there's a subtlety we haven't caught. If the latter, we should be using Xerces' own incremental parsing and running everything in a single thread, and thread lockups shouldn't be possible... or, at least, shouldn't be our problem. The handling of Xerces 1 hasn't changed in D13 except to invoke the methods via reflection so we don't have explicit compile-time dependencies specifically on Xerces1 or Xerces2.
