Developing a DSL Graphical Notation - Eclipse Modeling Project: A Domain-Specific Language Toolkit - page 163

Element Property Value

Constraint Body eventType = EventType::

INTERMEDIATE and triggerType =
TriggerType::MESSAGE

Feature Seq Initializer Element Class Event -> Element

Feature Value Spec Body EventType::INTERMEDIATE

Feature Event.eventType : EventType

Feature Value Spec Body TriggerType::MESSAGE

Feature Event.triggerType : TriggerType

Two Child Reference elements represent the two Event border items:
BorderedIntermediateEvent and BorderedMessageIntermediate
Event . These elements are stored in the Task 's events : Event Containment
Feature . For their Node Mapping , they use their corresponding Node defini-
tion but the same Creation Tool we use for these events when placed on the
diagram surface (Intermediate and Message Intermediate).
To distinguish border Event s, as they represent instances of the same Event
class from our domain model, we use Constraint and Feature Seq
Initializer elements. As shown in the mapping, both the eventType and
triggerType attributes are specified in the constraint and feature initialization.
The CollapsedSubprocess node is mapped in much the same manner, yet
it has no Child Reference elements. Section 4.5.6, “Subprocess Partition,”
covers how to use the Related Diagrams property of the Node Mapping ,
enabling us to double-click on a Process element and open it in a new diagram.

Gateways
All Gateway elements map in a similar manner because they all represent a
Gateway domain element initialized to different GatewayType enumeration lit-
erals. Table 4-28 gives the mapping, where, again, the Top Level Node
Containment Feature is set to our Process elements:Element reference.