]
Thomas Diesler updated JBVFS-143:
---------------------------------
Summary: file:// protocol URL might not work with 3rd party libraries (was: File
protocol URL might not work with 3rd party libraries)
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: