Community
Participate
Working Groups
- 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.
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.
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.
