org.jupe.editors.classdiagram.model
Class AddAdapter
java.lang.Object
org.eclipse.emf.common.notify.impl.AdapterImpl
org.jupe.editors.classdiagram.model.AddAdapter
- All Implemented Interfaces:
- org.eclipse.emf.common.notify.Adapter, org.eclipse.emf.common.notify.Adapter.Internal
public class AddAdapter
- extends org.eclipse.emf.common.notify.impl.AdapterImpl
The AddAdapter is needed for a work-around because in UML2 in case of adding
an element the corresponding event is fired before the attributes are set. So
we get i.e. a notification that a class is added but it has not yet a name,
which causes a problem when creating the diagram figures. This problem will
be solved this way: The ModelElement creates this adapter which handles only
the notification for the new name. After that the corresponding ModelElement
is created this new Element listens to all other notifications of the
corresponding UML2 object.
- Author:
- Emanuel Thomas, Michael Pradel
Nested classes/interfaces inherited from interface org.eclipse.emf.common.notify.Adapter |
org.eclipse.emf.common.notify.Adapter.Internal |
Method Summary |
void |
notifyChanged(org.eclipse.emf.common.notify.Notification notification)
|
Methods inherited from class org.eclipse.emf.common.notify.impl.AdapterImpl |
getTarget, isAdapterForType, setTarget, unsetTarget |
Methods inherited from class java.lang.Object |
equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
AddAdapter
public AddAdapter(NodeModelElement modelParent)
notifyChanged
public void notifyChanged(org.eclipse.emf.common.notify.Notification notification)
- Specified by:
notifyChanged
in interface org.eclipse.emf.common.notify.Adapter
- Overrides:
notifyChanged
in class org.eclipse.emf.common.notify.impl.AdapterImpl