Bug 191581 - [efs] Can't open new file created in remote project
Summary: [efs] Can't open new file created in remote project
Status: CLOSED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P2 major (vote)
Target Milestone: 2.0.1   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
: 198387 202528 (view as bug list)
Depends on:
Blocks: 187690
  Show dependency tree
 
Reported: 2007-06-07 16:24 EDT by Kevin Doyle CLA
Modified: 2007-09-10 09:07 EDT (History)
4 users (show)

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 Kevin Doyle CLA 2007-06-07 16:24:01 EDT 
After creating a new file in a remote project it tries to open the file right away and displays the error "File rse://SERVER/home/tester/kevin/test.php does not exist." inside the editor.  Closing and reopening the file displays the same error.

Steps to Reproduce:
1. Find a folder, right click, and select Create Remote Project.
2. Go to the Java/Resource perspective and right click on the project and select New File.
3. Give the file some name.
4. Error is displayed inside the editor opened for the new file.

-----------Enter bugs above this line-----------
TM 2.0RC2 Testing
installation : eclipse-SDK-3.3RC3
RSE install  : RSE 2.0 RC2
java.runtime : Sun 1.5.0_11-b03
os.name:     : Windows XP, Service Pack 2
------------------------------------------------
Comment 1 Martin Oberhuber CLA 2007-07-31 09:22:58 EDT 
*** Bug 198387 has been marked as a duplicate of this bug. ***
Comment 2 Martin Oberhuber CLA 2007-08-02 12:15:32 EDT 
Fixed, committed and released for I20070802-1215

[191581][efs] clear local IRemoteFile handle cache when modifying remote
   RSEFileStoreImpl.java
Comment 3 Kevin Doyle CLA 2007-08-24 16:49:55 EDT 
Verified with I20070823-0800.
Comment 4 Martin Oberhuber CLA 2007-09-10 09:07:59 EDT 
*** Bug 202528 has been marked as a duplicate of this bug. ***