|
Re: Bug: Input Stream not closed in unparsed-text(): msg#00154text.xml.saxon.help
Pier Fumagalli wrote: >So, IMVHO, in this case "reader.close()" makes more sense than >"is.close()". I concur, of course. I confess my "fix" was merely a test for verifying that not closing the basic InputStream was the actual problem I was seeing. I'd like to add that the InputStream (!) needs probably be closed also in the "catch (java.io.UnsupportedEncodingException encErr)" execution branch (the IS has already been opened here and will only be closed at garbage collection time if not closed explicitly). Rewriting the code a little (maybe using "finally") should do it. Regards, Christian. ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Bug: Input Stream not closed in unparsed-text(): 00154, Pier Fumagalli |
|---|---|
| Next by Date: | RE: does xsl:discard-document work with xsl:result-document?: 00154, Michael Kay |
| Previous by Thread: | Re: Bug: Input Stream not closed in unparsed-text()i: 00154, Pier Fumagalli |
| Next by Thread: | does xsl:discard-document work with xsl:result-document?: 00154, alan . painter-Jdski0UBDJ4AvxtiuMwx3w |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |