|
Hi,
I've got a problem with Xerces2
deserialization.
What's going on. I've got an application
which operates on multiparted HTTP message by filtering some parts.
This application reads from InputStream and parses data in standard way by
Xerces:
doc =
documentBuilder.parse(inputStream);
But after Xerces finishes, it closes the
inputStream and causes application fail.
Maybe you don't understand why not to close
after the inputStream.read() return EOF. Reason is that there's a chain of
filters e.g. for multipart message separation to parts, etc. Filters implements
InputStream and returning EOF indicates that actual part ends, but not
definitely file ends.
So, is it a bug or a feature Xerces closes the
stream?
Thanks very much.
Tobbi
|
