Bug 156797 - [refactoring] JDT Actions should check for registered ModelProvider and invoke validateChange
Summary: [refactoring] JDT Actions should check for registered ModelProvider and invok...
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-09-09 06:56 EDT by Franck Mising name CLA
Modified: 2009-08-30 02:06 EDT (History)
1 user (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 Franck Mising name CLA 2006-09-09 06:56:36 EDT 
JDT actions (e.g. org.eclipse.jdt.internal.ui.refactoring.reorg.DeleteAction) should check for ModelProvider's interested in the proposed resource changes, and invoke their validateChange method, like for example the core org.eclipse.ui.actions.DeleteResourceAction does.

Currently after registering a ModelProvider that warns not to delete some model's resources, trying to delete a model's resource in the Navigator will generate a warning message while the same resource can be silently deleted in the JDT's package explorer.
Comment 1 Martin Aeschlimann CLA 2006-09-20 10:52:25 EDT 
Are you sure this doesn't work? All our refactorings call validateChange. Delete is implemented as refactoring as well and I just debugged it down to the call.

Can you give a reproducible example?
Comment 2 Denis Roy CLA 2009-08-30 02:06:27 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.