Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321572 - [ComponentD] Can't drag/drop Class from root Package to Component
Summary: [ComponentD] Can't drag/drop Class from root Package to Component
Status: RESOLVED FIXED
Alias: None
Product: GMF-Tooling
Classification: Modeling
Component: Samples (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Michael Golubev CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 321567
Blocks:
  Show dependency tree
 
Reported: 2010-08-03 06:29 EDT by Christian Waniek CLA
Modified: 2012-12-11 15:12 EST (History)
1 user (show)

See Also:

Attachments
Patch to workaround the problem (2.50 KB, patch)
2010-08-03 06:32 EDT, Christian Waniek CLA 		borlander: iplog+
borlander: review+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Waniek CLA 2010-08-03 06:29:56 EDT 
Build Identifier: 

When I drag and drop a Class from the root Package to a Components content compartment it isn't shown any more.
This is due to the Class is put into the feature Component::nestedClassifier which isn't mapped so far.
Mapping of the feature isn't possible due to bug #321567

So attached you'll find a workaround (patch for the ComponentEditHelper) which ensures that  moved Elements are put into the right feature so they are shown in the diagram.

Reproducible: Always
Comment 1 Christian Waniek CLA 2010-08-03 06:32:15 EDT 
Created attachment 175760 [details]
Patch to workaround the problem
Comment 2 Michael Golubev CLA 2010-08-03 06:37:30 EDT 
Comment on attachment 175760 [details]
Patch to workaround the problem

Patch reviewed. 
Also it will fix the particular problem, we are considering the ways to generate the same code for all of other similar cases
Comment 3 Christian Waniek CLA 2010-08-03 06:58:07 EDT 
If bug #321567 is fixed this workaround becomes obsolete
Comment 4 Michael Golubev CLA 2010-09-10 07:36:23 EDT 
Patch committed, the problem is fixed now. 

Although, despite the fact that bug #321567 really represents the GMF problem, the solution described there won't fix this particular problem so these 2 scrs has nothing in common.