Bug 243222 - [Connections] invalidating notation model by default property-tab-usage
Summary: [Connections] invalidating notation model by default property-tab-usage
Status: NEW
Alias: None
Product: GMF-Runtime
Classification: Modeling
Component: General (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 normal
Target Milestone: ---   Edit
Assignee: gmf.ui-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-05 15:25 EDT by Thomas Beyer CLA
Modified: 2010-07-19 21:58 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Beyer CLA 2008-08-05 15:25:06 EDT
Build ID: I20080617-2000

Steps To Reproduce:
1. Generate any GMF-RCP which allows connections.
2. Create a connection with one node as source and one node as target as well as several other diagram-nodes.
3. Click on the source or target element in the properties view. Add some more nodes in the popped up menu and confirm the changes change.


More information:
The described steps above result in changes of the domain model according to the settings in the popped-up menu.
Issue 1: Every change made through this menu is reflected in the domain model, regardless of the underlying dsl (ecore-model) or ocl-constraints set in the mapping-model.
Issue 2: The changes do not effect the notation-model. Most-likely changes made by the menu result in invalidation and deletion of the connection in the notation model.

I think, the default behavior of generated code should not allow the user to invalidate its models by any chance. 
I cannot allow my clients to use this feature (which unfortunately already happened) and therefore I have to implement my own solution. 
Generally I try to use generated code as intensive as possible.
Therefor I would prefer a simple PropertySource as a first shot, that only shows the connection source and target. (Changes can still be made via the diagram).
Nevertheless it would be a very nice future feature, if the menu worked properly, meaning, only reasonable nodes can be choosen as source and target, according to the dsl as well as link-constraints. Also the amount of possible source and target edges should be taken into account.
Comment 1 Eclipse Webmaster CLA 2010-07-19 21:58:20 EDT
[GMF Restructure] Bug 319140 : product GMF and component
Runtime was the original product and component for this bug