[jboss-jira] [JBoss JIRA] Reopened: (JBVFS-147) Cannot read from vfs: protocol URL

[Thomas Diesler (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBVFS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler reopened JBVFS-147:
----------------------------------



John,

did you consider the case where I might not be the first who sees the file?

In case of the structure deployer processing there might be an AbstractVFSArchiveStructureDeployer processing the vfile before my AbstractVFSStructureDeployer sees it. When I see the vfile it might already be mounted. In that case how do I get hold of the MountHandle?

Generally, I believe that vfile.getChild(), vfile.openStream() and friends should behave in a deterministic way independent of what processing another component did previously. 

One possible way out of this might be to always provide access to the "virgin" source of the vfile.   


> Cannot read from vfs: protocol URL
> ----------------------------------
>
>                 Key: JBVFS-147
>                 URL: https://jira.jboss.org/jira/browse/JBVFS-147
>             Project: JBoss VFS
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.0.CR3
>            Reporter: Thomas Diesler
>            Assignee: John Bailey
>             Fix For: 3.0.0.CR4
>
>
> Cannot read bytes from vfs: protocol URL
> URL url = new URL("vfs:/home/tdiesler/svn/jboss-osgi/projects/testing/trunk/target/test-libs/example-simple.jar/");
> URLConnection con = (URLConnection)url.openConnection();
> InputStream inputStream = con.getInputStream();
> int read = inputStream.read();
> read is -1

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira