Bug 538650

Summary:	Create instance operation leads to changing other objects feature
Product:	[Modeling] Sirius	Reporter:	Yvan Lussaud <yvan.lussaud>
Component:	Diagram	Assignee:	Project Inbox <sirius.diagram-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	pierre-charles.david
Version:	5.1.2	Keywords:	triaged
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Yvan Lussaud

2018-09-05 09:35:53 EDT

- create a container mapping for an EClass that have a feature name for instance
- create a node mapping for a children of this class that also have a feature name
- create a creation tool for the children object
 - set the feature to a not existing value
 - set the name of the children

behavior:
 - a stack trace
 - the container name is changed

expected behavior:
 - a stack trace (or something prettier if possible)

My guess is the children is created successfully but when the containment feature can't be setted an exception is thrown skipping the change context to the created object, then the content of the create instance is executed in the container context.

Comment 1 Pierre-Charles David

2018-09-05 11:55:06 EDT

Not sure it's exactly the same issue but it sounds related to something I tried to fix a while ago, see https://git.eclipse.org/r/c/68025.

IIRC, we decided not to merge this at the time because some existing modelers relied on the existing broken behavior, but I could be wrong, it was a while ago.

Comment 2 Pierre-Charles David

2018-09-05 11:58:09 EDT

Actually, there was a ticket created for the other related issue that the patch does not reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=489023

I think this may be different symptoms of the same root cause.