2008/3/10, Griffith, Michael * <[EMAIL PROTECTED]>:
>
> I believe (maybe incorrectly so) that the problem is caused by the
> XSLTResult calling close/flush when processing the result.



Mmm... It reminds me a thing.
When processing an XML file via a XML parser, the parser closes the stream
at the end!
To work around this problem, I had to wrap the original InputStream into an
object that overrides the "close" method, not closing the stream.

Antonio

Reply via email to