Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 334360

Summary: No update of diagram view after adding edges programmatically using EMF reflective API
Product: [Modeling] GMF-Runtime Reporter: Grit Dudeck <grit.du>
Component: NotationAssignee: Project Inbox <gmf-notation-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 2.1   
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard:

Description Grit Dudeck CLA 2011-01-14 04:57:00 EST 
Build Identifier: 

The following scenario:

A UML model is opened within the MDT Papyrus Editor (or another GMF based Editor such as RSA UML Modeler). Now, an existing association between two classes can be added to a diagram that contains the two classes. However, if I apply this change to the opened model without using the editor, but using the EMF reflective API, the edge is added correctly to the *.notation model but the diagram view is not updated. The Editor has to be closed and reopened again to see the change. The changes are applied to the model using the transactional editing domain of the opened editor. The update issue occurs only when adding edges to the notation model. All other changes to the business model or the graphical model are updated correctly in the model explorer and the diagram view. 

Reproducible: Always

Steps to Reproduce:
Example:

1. create a simple UML model with Papyrus (2 classes and 1 association between these classes)
2. add the classes to the diagram view (without association)
3. add the edge using EMF reflective API and the transactional editing domain

The diagram is not updated. After reopening the editor, the edge is seen.
Comment 1 Pierre-Charles David CLA 2022-12-28 10:04:46 EST 
Eclipse GMF Notation is moving away from this bugs.eclipse.org issue tracker to
https://github.com/eclipse/gmf-notation.

If this issue is relevant to you and still present in the latest release:

* Create a new issue at https://github.com/eclipse/gmf-notation/issues/.
  * Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  * In the GitHub description, start with a link to this bugzilla ticket
  * Optionally add new content to the description if it can helps towards resolution
* Update bugzilla ticket
  * Add to "See also" property (up right column) the link to the newly created GitHub issue
  * Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  * Set status as CLOSED MOVED

All issues that remain open will be automatically closed in the next few weeks. Then
the Bugzilla component for GMF Notation will be archived and made read-only.
Comment 2 Pierre-Charles David CLA 2023-02-05 11:15:32 EST 
Closing as part of the move to GitHub.
Feel free to re-open an equivalent issue at https://github.com/eclipse/gmf-notation/issues if you feel this is still relevant.