Java Reference
In-Depth Information
object).getAdapter(IPropertySource.class);
}
return null;
}
This displays the properties of selected items for edit in the
Properties
view,
but only if they are of the same type. However, we want only properties that
make sense to change on multiple elements at a time to be editable. It doesn't
make sense to change all the requirement IDs to the same value, for example. We
leave this refinement as a future enhancement and move on to our next diagram.
As mentioned already, we want to leverage the BPMN notational elements for
our Scenario diagram. Unfortunately, no BPMN2 diagramming component
exists within MDT, and the BPMN project within the SOA Tools project uses an
older version of GMF and does not generate its figures to a standalone plug-in.
Fortunately, this gives us an opportunity to show how this is done as we develop
this diagram.
4.5.1 Graphical Definition
The BPMN specification defines many notational elements. We start with those
to be used in our scenario diagram, but the idea is to create a figures plug-in that
can be reused as a reusable library for any BPMN-based diagram. To begin, we
create a new
org.eclipse.dsl.bpmn
project and, within it, a new
bpmn.
gmfgraph
model in the
/diagrams
folder. In this case, we're interested in only
the graphical definition, which we can use to generate a standalone plug-in and
mirrored.gmfgraph
model that we'll be referencing in our scenario diagram
definition.
TIP
Some workflow issues arise when dealing with standalone figure bundles,
so it's typically easier to first develop the default way using figures gener-
ated and included in the generator model. When the diagram is mostly
completed, generate the figure bundle and load the
mirrored.
gmfgraph
model into your mapping model to change references.
Search WWH ::
Custom Search