Bug 30823 - [Navigator] RenameResourceAction.invokeOperation should use validateEdit/setContents
Summary: [Navigator] RenameResourceAction.invokeOperation should use validateEdit/setC...
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Knut Radloff CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-03 12:12 EST by Knut Radloff CLA
Modified: 2003-02-03 18:56 EST (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 Knut Radloff CLA 2003-02-03 12:12:26 EST 
build 20030129

RenameResourceAction.invokeOperation deletes an existing target resource before 
moving the source. 
When the target resource is an existing file it should be renamed by calling 
setContents instead of deleting the conflicting resource and then moving the 
source. If it is read-only validateEdit should additionally be called before 
doing the setContents. If the source file is read-only as well, validateEdit 
needs to be called for the source and the destination together.
Comment 1 Knut Radloff CLA 2003-02-03 18:56:19 EST 
Fixed in >20030203. Using setContents if rename destination exists and 
additionally calling validateEdit if rename destination is read-only.