[jira] [Resolved] (JENA-6) Need a consistent policy on closing streams for Jena readers

["Andy Seaborne (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JENA-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne resolved JENA-6.
------------------------------

       Resolution: Fixed
    Fix Version/s: Jena 2.10.0

[[Largely overtaken by events (new RIOT readers in Jena 2.10.0)]]

There should systematic handling with stream no closed if a stream is handed in.
                
> Need a consistent policy on closing streams for Jena readers
> ------------------------------------------------------------
>
>                 Key: JENA-6
>                 URL: https://issues.apache.org/jira/browse/JENA-6
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: RIOT
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Minor
>             Fix For: Jena 2.10.0
>
>
> See also https://sourceforge.net/tracker/?func=detail&aid=3067790&group_id=40417&atid=430288
> Jena readers do not provide any gaurantees as to the state of the stream in terms of byte position after parsing.  RIOT, and some original readers, also close the stream, on the principle the stream is no longer usable.
> But Java zip streams signal end of stream but can continue to be read by moving to the next zip file entry.  Closing the stream after parsing is wrong in this case.
> The original report noted a wrapper can be used that does not pass through the .close.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira