underlying CharReader is closing InputStream / Reader PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3119 *** shadow/3119 Tue Aug 14 08:00:27 2001 --- shadow/3119.tmp.6990 Tue Aug 14 08:00:28 2001 *************** *** 0 **** --- 1,46 ---- + +============================================================================+ + | underlying CharReader is closing InputStream / Reader | + +----------------------------------------------------------------------------+ + | Bug #: 3119 Product: Xerces-J | + | Status: NEW Version: 1.4.2 | + | Resolution: Platform: All | + | Severity: Critical OS/Version: All | + | Priority: Other Component: Core | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + the CharReader class is closing the + Reader it was supplied with, though it + doesn't own it, and isn't allowed to close + the reader. + + From org/apache/xerces/framework: + parse(...): + Parses the input source specified by the given system identifier. + This method is <em>almost</em> equivalent to the following: + parse(new InputSource(systemId)); + The only difference is that this method will attempt to close + the stream that was opened. + + the parse(InputSource source) method isn't allowed to close + the Reader the InputSource holds. + + at /org/apache/xerces/readers/CharReader.java:172 + // + // We have reached the end of the stream. + // + fCharacterStream.close(); + fCharacterStream = null; + + The fix would be to not close the fCharacterStream... + + I found this bug while trying to receive an XML-File + via an InputStream and writing over the Socket back + an result, but the closing of the InputStream closed + also the OutputStream of the Socket... + + sincerely yours, michael ehrmann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
