You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary D. Gregory (JIRA)" <ji...@apache.org> on 2012/06/01 03:49:23 UTC

[jira] [Commented] (VFS-419) JarFileSystem incorrectly resolves file if it has been removed from the cache

    [ https://issues.apache.org/jira/browse/VFS-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287090#comment-13287090 ] 

Gary D. Gregory commented on VFS-419:
-------------------------------------

I added 

https://svn.apache.org/repos/asf/commons/proper/vfs/trunk/core/src/test/java/org/apache/commons/vfs2/provider/jar/test/JarAttributesTestCase.java

which I thought would show the need for implementing the {{createFile}} method, but the tests pass without it.

So I am still looking for a test that:
# shows the method is required
# shows that the method should do more than just {{return new JarFileObject(name, null, this, false);}}
                
> JarFileSystem incorrectly resolves file if it has been removed from the cache
> -----------------------------------------------------------------------------
>
>                 Key: VFS-419
>                 URL: https://issues.apache.org/jira/browse/VFS-419
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Sergey Grigorev
>              Labels: core, patch
>             Fix For: 2.0
>
>         Attachments: JarFileSystem.java.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> If I call fileSystemManager.resolveFile("jar: ... ") and the file was removed from cache, JarFileSystem calls method createFile(AbstractFileName name). This method is not overridden from ZipFileManager and works wrong (its return ZipFileObject instead JarFileObject). But i can override it and make return JarFileObject case this object won't have children and JarURLConnectionImpl won't work. It should reinvalidate cache and return the object with children objects.
> I've added a patch to fix this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira