Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337856 - UnitApplication's undo() changes graph
Summary: UnitApplication's undo() changes graph
Status: RESOLVED FIXED
Alias: None
Product: EMFT.Henshin
Classification: Modeling
Component: Interpreter (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Enrico Biermann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-22 11:09 EST by Felix Rieger CLA
Modified: 2011-03-09 05:20 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 Felix Rieger CLA 2011-02-22 11:09:06 EST 
There is a problem with UnitApplication's undo() method: When a UnitApplication is un-done (either manually or automatically when it fails), certain references can change their order. This changes the graph and can lead to Rules or TransformationUnits acting unexpectedly, even though loading the model graph, executing a UnitApplication and calling undo() should be equivalent to just loading the model graph.
Comment 1 Enrico Biermann CLA 2011-02-28 07:21:46 EST 
The correct order of eobjects in reference lists should now be correctly restored for undo() and redo().
Comment 2 Enrico Biermann CLA 2011-02-28 14:21:31 EST 
I have reverted the changes for now and reopened this bug. The update broke more than it fixed.
Comment 3 Enrico Biermann CLA 2011-03-02 04:28:32 EST 
The new bugs should be fixed and undo() should work. I leave this bug open for now, in case some more problems occur.
Comment 4 Enrico Biermann CLA 2011-03-09 05:20:48 EST 
It seems to work fine now.