[
https://issues.apache.org/jira/browse/VFS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Lee closed VFS-225.
-------------------------
Fix Version/s: 2.7.0
Resolution: Fixed
> File name parsing issues in layered file systems
> ------------------------------------------------
>
> Key: VFS-225
> URL: https://issues.apache.org/jira/browse/VFS-225
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Windows XP SP2 - but also assuming in other environments
> Reporter: Jens Scheffler
> Priority: Major
> Fix For: 2.7.0
>
> Attachments: LayeredFileNameParsingTest.java
>
>
> 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(AbstractFileSystem.java:274)
> at
> org.apache.commons.vfs.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:267)
> at
> org.apache.commons.vfs.provider.AbstractFileObject.resolveFile(AbstractFileObject.java:670)
> at
> de.jensscheffler.ftpsync.db.SyncFileSystemTest.treeCopy(SyncFileSystemTest.java:87)
> (...)
> 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 was sent by Atlassian Jira
(v8.3.4#803005)