[jboss-jira] [JBoss JIRA] Commented: (JBVFS-143) file:// protocol URL might not work with 3rd party libraries

[John Bailey (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBVFS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12519884#action_12519884 ] 

John Bailey commented on JBVFS-143:
-----------------------------------

VFS will no longer be using file:// URLs.  VFS will be using vfs:// ULRs moving forward.  This will cause this case, as well as most other 3rd party integrations to delegate to raw URL handling.  When this occurs, normal URL connections will not work if the archive has been mounted as it will be referencing a directory.  

Please see JBVFS-147 and JBVFS-142 for more details.  

> file:// protocol URL might not work with 3rd party libraries
> ------------------------------------------------------------
>
>                 Key: JBVFS-143
>                 URL: https://jira.jboss.org/jira/browse/JBVFS-143
>             Project: JBoss VFS
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.0.CR3
>            Reporter: Thomas Diesler
>            Assignee: John Bailey
>            Priority: Critical
>             Fix For: 3.0.0.CR4
>
>
> A URL like this
> file:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/example-http.jar/res/message.txt
> gets passed to a 3rd party library (i.e. Jetty)
> which does stuff like this
>     public static Resource newResource(URL url, boolean useCaches)
>     {
>         if (url==null)
>             return null;
>         String url_string=url.toExternalForm();
>         if( url_string.startsWith( "file:"))
>         {
>             try
>             {
>                 FileResource fileResource= new FileResource(url);
>                 return fileResource;
>             }
>             catch(Exception e)
>             {
>                 Log.debug(Log.EXCEPTION,e);
>                 return new BadResource(url,e.toString());
>             }
>         }
>         else if( url_string.startsWith( "jar:file:"))
>         {
>             return new JarFileResource(url, useCaches);
>         }
>         else if( url_string.startsWith( "jar:"))
>         {
>             return new JarResource(url, useCaches);
>         }
>         return new URLResource(url,null,useCaches);
>     }
> As a consequence, content access does not work. 
> This seems to be a general issue caused by the reuse of the well known file:// protocol which may be processed explicitly by 3rd party libs.

-- 
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