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

The second mapping uses the children containment reference as the
Target Feature and has its own Tool . Our final mapping is for Dependency
links. As you will recall from our graphical definition, these are blue dashed lines
with open arrow head target decorations. We can use them to indicate depend-
ency references between Requirement s, as shown in Table 4-18.

Table 4-18 Requirements Dependency Link Mapping

Element Property Value

Mapping

Link Mapping Target Feature dependencies : Requirement

Diagram Link Connection Dependency

Tool Creation Tool Dependency

4.4.4 Generation

As before, we can right-click on our mapping model and select Create Generator
Model to bring up the transformation dialog. The default requirements.
gmfgen in the /diagrams folder is fine, so we proceed to the Select Mapping
Model page, where our requirements.gmfmap model is already loaded. On
the next page, we find that our requirements.genmodel is already selected
and loaded as well. On the final page, we keep the defaults Use IMapMode and
Utilize Enhanced Features of GMF Runtime , and then click Finish .
We now leave the default generation properties for the moment and generate
our diagram plug-in using the Generate Diagram Code option from the file's con-
text menu. Launching the runtime workspace lets us create a new requirements
diagram using the generated wizard found in the Examples category of the New
( Ctrl+N ) dialog. Figure 4-19 is a sample diagram.
You'll notice right away that creating two RequirementGroup objects on
the diagram, followed by linking these groups using the Child Group tool,
requires pressing F5 to invoke a refresh to see the link. We need to modify the
generated code to invoke a canonical update to avoid this, as we did in our
mindmap with the override of handleNotificationEvent() .