commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miroslav Pokorny (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (VFS-358) RamFileRandomAccessContent.close() does *NOT* call RamFileObject.close().
Date Mon, 25 Jul 2011 13:37:09 GMT

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

Miroslav Pokorny updated VFS-358:
---------------------------------

    Summary: RamFileRandomAccessContent.close() does *NOT* call RamFileObject.close().  (was:
RamFileRandomAccessContent.close() does call RamFileObject.close().)

> RamFileRandomAccessContent.close() does *NOT* call RamFileObject.close().
> -------------------------------------------------------------------------
>
>                 Key: VFS-358
>                 URL: https://issues.apache.org/jira/browse/VFS-358
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: Miroslav Pokorny
>
> The problem manifests itself if one uses RandomAccessContent from a FileObject which
is from ram://. Closing any stream from the RAC does not cleanup some counters which means
future calls to FileObject.isContentOpen() return true which is wrong because the RAC.close().
> The fix to RamFileRandomAccessContent.close() is a simple one liner.
>     /*
>      * (non-Javadoc)
>      * 
>      * @see org.apache.commons.vfs.RandomAccessContent#close()
>      */
>     @Override
>     public void close() throws IOException {
>         // do not try and call rafis.close() which does nothing but call this method.
>         this.file.close();
>     }

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message