commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman (JIRA)" <>
Subject [jira] Commented: (VFS-225) File name parsing issues in layered file systems
Date Sat, 15 Nov 2008 15:36:47 GMT


James Carman commented on VFS-225:

I wouldn't suggest writing a test case that uses "c:/" at all.  Our automated builds don't
run on windows machines, so those tests would fail.  What's wrong with creating a ZIP file
and including in as a test resource.  Then use that to test the logic?

> File name parsing issues in layered file systems
> ------------------------------------------------
>                 Key: VFS-225
>                 URL:
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: Windows XP SP2 - but also assuming in other environments
>            Reporter: Jens Scheffler
> The "!" character is used as delimiter for e.g. ZIP file access as VFS component.
> When trying to traverse a layered file, e.g. traversing a ZIP content and the ZIP contains
a file with a "!" in the file name itself then a FileSystemException appears - it seems that
the parsing routine for layered filenames is stumbling over the "!" character.
> Exception trace for a test VFS component:
> org.apache.commons.vfs.FileSystemException: Incorrect file system URI "syncdb:file:///C:/Temp/test.xml!/c/temp/Maps/Important
to Read!!/" in name "syncdb:file:///C:/Temp/test.xml!/c/temp/Maps/Important to Read!!.txt",
was expecting "syncdb:file:///C:/Temp/test.xml!/".
> 	at org.apache.commons.vfs.provider.AbstractFileSystem.resolveFile(
> 	at org.apache.commons.vfs.provider.AbstractFileSystem.resolveFile(
> 	at org.apache.commons.vfs.provider.AbstractFileObject.resolveFile(
> 	at de.jensscheffler.ftpsync.db.SyncFileSystemTest.treeCopy(
> 	(...)
> As the accessing code was just traversing a folder tree with no chance to handle this,
is there any alternative for traversing through these layered file systems when the content
contains special characters?
> Maybe the approach for parsing needs to be enhanced also, I could offer some help but
maybe need a hint to contribute a fix.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message