Bug 328232 - EditHelper getDestroyDependentCommand ignored when a specific IClientContext is required
Summary: EditHelper getDestroyDependentCommand ignored when a specific IClientContext ...
Status: NEW
Alias: None
Product: GMF-Runtime
Classification: Modeling
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 328506
  Show dependency tree
 
Reported: 2010-10-20 07:07 EDT by Yann Tanguy CLA
Modified: 2010-10-22 15:15 EDT (History)
0 users

See Also:

Attachments
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 Yann Tanguy CLA 2010-10-20 07:07:40 EDT 
Currently using the ExtensibleType framework in a way that requires IClientContext to be provided explicitly, it seems that the getDestroyDependentCommand from EditHelper never gets called.

These EditHelper directly inherit from AbstractEditHelper. This may be related to the fact the ElementType is sometimes retrieved (see: getDestroyElementWithDependentsCommand or getDestroyElementCommand) from the registry without providing the client context.
e.g.
protected ICommand getDestroyElementCommand(DestroyElementRequest req) {
		...
			if (parentMap != null) {
    			parentType = (IElementType) parentMap
    				.get(RequestCacheEntries.Element_Type);
			} else {
			    parentType = ElementTypeRegistry.getInstance().getElementType(parent); 
		...