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

Bug 365955

Summary: Top level nodes appear twice when being dragged and dropped into nested nodes
Product: [Modeling] GMF-Runtime Reporter: Thomas Buchmann <bkunlimited>
Component: NotationAssignee: Project Inbox <gmf-notation-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: major    
Priority: P3    
Version: 2.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Ecore Model
none
gmfgraph model
none
gmftool model
none
mapping model none

Description Thomas Buchmann CLA 2011-12-07 15:07:52 EST 
Build Identifier: 20110916-0149

If a container element is mapped on the diagram canvas and also to nodes that have a compartment, all contained elements that have been added to the diagram canvas appear twice when being dragged and dropped into other containers.

I created a small demo project realizing a very simplified form of UML2 package diagrams to demonstrate the issue. 

All intermediate models seem to be fine, so the problem seems to be in the GMF notation framework. 

Reproducible: Always

Steps to Reproduce:
1. Start the GMF Editor from the project i attached to this bug report.
2. Create a package and a class as a top level node.
3. Now save and drag & drop the class into the package.
Comment 1 Thomas Buchmann CLA 2011-12-07 15:08:49 EST 
Created attachment 208063 [details]
Ecore Model
Comment 2 Thomas Buchmann CLA 2011-12-07 15:09:16 EST 
Created attachment 208064 [details]
gmfgraph model
Comment 3 Thomas Buchmann CLA 2011-12-07 15:09:36 EST 
Created attachment 208065 [details]
gmftool model
Comment 4 Thomas Buchmann CLA 2011-12-07 15:12:10 EST 
Created attachment 208066 [details]
mapping model
Comment 5 Pierre-Charles David CLA 2022-12-28 10:04:26 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 6 Pierre-Charles David CLA 2023-02-05 11:15:27 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.