Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348218 - Change lower bound of transformationSystem edge to forbid Rules from not having a TransformationSystem
Summary: Change lower bound of transformationSystem edge to forbid Rules from not havi...
Status: RESOLVED FIXED
Alias: None
Product: EMFT.Henshin
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-03 10:40 EDT by Felix Rieger CLA
Modified: 2012-02-02 08:48 EST (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 Felix Rieger CLA 2011-06-03 10:40:00 EDT 
The henshin model currently contains an edge from Rule to TransformationSystem (name: transformationSystem, opposite edge of the Rule containment edge), lower bound 0, upper bound 1.
However, it doesn't make any sense to have a Rule without a TransformationSystem, so this should at be set to lower bound 1, upper bound 1, if not removed completely. 

Also, neither Graphs nor TransformationUnits have a transformationSystem edge like Rules, which could be changed for more consistency, i.e. either dropping the transformationSystem edge for Rules or adding transformationSystem edges for TransformationUnits and Graphs.
Comment 1 Daniel Strueber CLA 2011-08-08 12:37:11 EDT 
The reasoning for setting the bounds to 0..1 in the first place was to ease support for a composite transformation meta-model, an extension of the Henshin meta-model that conceives Rules which are contained in other Rules.
Comment 2 Felix Rieger CLA 2012-02-02 08:48:00 EST 
The new model will allow nested Rules, so this bug is no longer relevant.