Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316548 - [class diagram] restore related elements not available after deleted association
Summary: [class diagram] restore related elements not available after deleted association
Status: RESOLVED DUPLICATE of bug 343641
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P1 enhancement (vote)
Target Milestone: 0.8.0   Edit
Assignee: Patrick Tessier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-10 17:59 EDT by Raphael Faudou CLA
Modified: 2011-09-29 03:44 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 Raphael Faudou CLA 2010-06-10 17:59:37 EDT 
create two classes C1 and C2 and an association A_C1-C2 between those classes.
Delete from diagram the association
Then select one of the classes (any) and request "navigate>restore related element". This command is no more available (it was before and there was a NPE on it) and it should be.
Workaround : serach for the association in the model explorer and drag and drop it, but we really need to get the "restore related elements" active in this situation. Major as it is a key behavior to ensure "valid" diagrams.
Comment 1 Patrick Tessier CLA 2011-01-04 05:03:17 EST 
According documentation about this functionality. the code to do this job is not generic and not generated. So we have to code it by implement editpolicy that can manage ShowRelatedElementsRequest.
I put it as an enhancement with a high priority.
Comment 2 Arthur Daussy CLA 2011-09-29 03:44:50 EDT 
This problem will be corrected with the following bug:
343641: [General] "Restore related elements" action on Class Diagram, Activity Diagram and Parametric Diagram poluating other GMF editors
https://bugs.eclipse.org/bugs/show_bug.cgi?id=343641

*** This bug has been marked as a duplicate of bug 343641 ***