[JBoss JIRA] Created: (JBVFS-143) File protocol URL might not work with 3rd party libraries
by Thomas Diesler (JIRA)
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
14 years, 10 months
[JBoss JIRA] Created: (JBVFS-138) Issues with symboic links in VFS3
by John Bailey (JIRA)
Issues with symboic links in VFS3
---------------------------------
Key: JBVFS-138
URL: https://jira.jboss.org/jira/browse/JBVFS-138
Project: JBoss VFS
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0.CR1
Reporter: Ales Justin
Assignee: John Bailey
Fix For: 3.0.0.CR2
If a filesystem is mounted for a path that contains a symbolic link, it will only mount at the path provided at mount time. In other words if you mount it using the canonical path, it will not be accessible using the path containing the symlink. The same is true for the opposite case.
Ex.
Link: /path/with/link --> /path/without/link
Mount: /path/without/link/archive.ear
Mount: /path/without/link/archive.ear/archive.jar
Access: new URL("file:///path/with/link/archive.ear/archive.jar") <--- This is fail as /path/with/link/archive.ear/archive.jar does not point to the mounted filesystem. It will default to the RealFilesystem and archive.jar will not exist.
--
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
14 years, 10 months