Re: Xerces appears to close user managed InputStream

2008-10-16 Thread Michael Glavassevich
Hi Jeff, It's working as designed. The API doc [1] for the SAX InputSource says: " ... standard processing of both byte and character streams is to close them on as part of end-of-parse cleanup, so applications should not attempt to re-use such streams after they have been handed to a parser." If

Xerces appears to close user managed InputStream

2008-10-16 Thread Jeffrey Sinclair
j-users, I'm finding that Xerces is closing a user managed InputStream which I'm not expecting. Am I correct in thinking this is a bug and I should proceed with submitting a JIRA? The following JUnit test demonstrates this: /** * Tests that a simple build does not closed the original (use