I don't think there's any way to run Xerces purely as a pipeline at this time, unless I missed an announcement.
The easiest solution would be to plug an "identity filter" stage into your text pipeline, providing blocking for the parser's reads and (if necessary) for the text source's writes... but that does require that the code generating the text and the parser run in separate threads. ______________________________________ Joe Kesselman / IBM Research --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
