Bug 199394 - Files and folders with #virtual# in the name are not properly handled
Summary: Files and folders with #virtual# in the name are not properly handled
Status: NEW
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P4 minor (vote)
Target Milestone: Future   Edit
Assignee: Xuan Chen CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-09 06:35 EDT by Martin Oberhuber CLA
Modified: 2008-09-29 09:47 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-08-09 06:35:51 EDT 
RSE uses #virtual# as separator to indicate virtual files in an archive.

But, there can also be real files in the file system with #virtual# in their path. This is particularly the case when looking at the RemoteSystemsTempFiles project after user has browsed into ZIP or TAR archives on a remote system.

LocalFileService and DStoreFileService need to check whether a file actually exists on the local disk, before assuming it is virtual in an archive.

This is related to bug #199276, which is a similar issue with archive extensions.
Comment 1 Martin Oberhuber CLA 2007-08-09 06:39:32 EDT 
For Local, I think I fixed at least part of the issue, by checking first whether the file physically exists and is a file or folder, before asking the archive manager:

[199394] Allow real files/folders containing String #virtual#
    LocalFileService   1.13

Changed 
   LocalFileService#getFile(),
   LocalFileService#internalFetch()
but it needs more review if other methods are affected as well, more thorough testing, and review in dstore as well.
Comment 2 Martin Oberhuber CLA 2007-10-01 07:57:29 EDT 
Bulk update target milestone 2.0.1 -> 3.0