Skip to main content
Jump to: navigation, search

Difference between revisions of "STP/BPMN Component/STP BPMN Presentation Hands on tutorial"

(Adding a drop action)
(Adding a drop action)
Line 250: Line 250:
== Adding a drop action ==
== Adding an annotation through a drag and drop action ==
We want to have some more interaction now, and the best way to do that for the end-user is to do some drag and drop on the diagram.
We are going to use a Participant view that will be complete enough to represent some participants.
We will see how to drop them on the diagram just next.
== The participant view ==

Revision as of 19:05, 3 March 2007

This tutorial is presented as part of the STP BPMN Presentation at EclipseCon 2007.


In this section, we are going to begin to play with the modeler and try to extend its use.

We want to add a participant to our shapes. A participant represents a person with a name and a role.

Adding a property tab to create your annotation

The easiest way to add a participant to your shape is to create a property tab to represent it and enable us to enter his name and his role.

You will need to add, org.eclipse.stp.bpmn and org.eclipse.stp.bpmn.diagram into the dependencies of the plugin.

Your file should contain these dependencies:

Require-Bundle: org.eclipse.ui,

In the plugin.xml file, we define a new property tab named "Participants". We add one section to the tab.

The contributor for the new tab, it defines a new category

        <propertyCategory category="Participants"/>

The definition of the tab itself

   <extension point="">
     <propertyTabs contributorId="">

The definition of the section inside the property tab

   <extension point="">
     <propertySections contributorId="">
           <input type="org.eclipse.stp.bpmn.Activity"/>
           <input type="java.lang.Object"/>

Now we are going to code the tab itself.

A tab is an instance of AbstractPropertySection.

Create a class in as ParticipantPropertySection.

Two methods are important there :

the property tab UI is defined in createPartControl, and the input management in setInput. We need to implement those two methods.

Let's create a first version of createPartControl, with two text fields:

       * Creates the UI of the section.
       public void createControls(Composite parent, 
               TabbedPropertySheetPage aTabbedPropertySheetPage) {
               super.createControls(parent, aTabbedPropertySheetPage);
               GridLayout layout = new GridLayout(2, false);
               GridData gd = new GridData(SWT.FILL);
               gd.minimumWidth = 500;
               gd.widthHint = 500;
               getWidgetFactory().createCLabel(parent, "Name");
               nameText = getWidgetFactory().createText(parent, "");
               getWidgetFactory().createCLabel(parent, "Role");
               roleText = getWidgetFactory().createText(parent, "");

Now let's handle the data.

       * Manages the input.
       public void setInput(IWorkbenchPart part, ISelection selection) {
               super.setInput(part, selection);
               if(selection instanceof IStructuredSelection) {
                       Object unknownInput = 
                              ((IStructuredSelection) selection).getFirstElement();
                       if (unknownInput instanceof IGraphicalEditPart && 
                               (((IGraphicalEditPart) unknownInput).
                                       resolveSemanticElement() != null)) {
                                unknownInput = ((IGraphicalEditPart) unknownInput).resolveSemanticElement();
                       if (unknownInput instanceof Activity) {
                                       Activity elt = (Activity) unknownInput;
                                       EAnnotation ea = elt.getEAnnotation(ParticipantConstants.PARTICIPANT_ANNOTATION);
                                       if (ea != null) {
                                               nameText.setText((String) ea.getDetails().get(ParticipantConstants.PARTICIPANT_NAME));
                                               roleText.setText((String) ea.getDetails().get(ParticipantConstants.PARTICIPANT_ROLE));
                                       activity = (Activity) elt;
               activity = null;

We now have a working section. Hopefully.

We need to make sure that the changes in the text fields are reflected in the EAnnotation. To do this, we need to add a ModifyListener on the text fields. Plus we need to create a command or use an existing one to do the job of modifying the resource in a transaction. We choose to create our own command, we could also have used a chain of commands with EMF.

        * Utility class that finds the files and the editing domain easily,
        * Abstractas the doExecuteWithResult method needs to be implemented.
        * @author <a href="">Hugues Malphettes</a>
        * @author <a href="">Antoine Toulmé</a>
        * @author <a href="">© Intalio, Inc.</a>
       private abstract class ModifyParticipantEAnnotationCommand extends AbstractTransactionalCommand {
       public ModifyParticipantEAnnotationCommand(Activity ann, String label) {
                super((TransactionalEditingDomain) AdapterFactoryEditingDomain.getEditingDomainFor(ann), label, getWorkspaceFiles(ann));

We implement our text listener directly in the class.

        * Tracks the change occuring on the text field.
        * @author <a href="">Hugues Malphettes</a>
        * @author <a href="">Antoine Toulmé</a>
        * @author <a href="">© Intalio, Inc.</a>
      private class ModifyParticipantInformation implements ModifyListener {
               private String key;
               private Text field;
               public ModifyParticipantInformation(String k, Text field) {
                       key = k;
                       this.field = field;
               public void modifyText(ModifyEvent e) {
                       if (activity == null) { // the value was just initialized
                       ModifyParticipantEAnnotationCommand command = 
                               new ModifyParticipantEAnnotationCommand(activity, "Modifying participant") {
                               protected CommandResult doExecuteWithResult(IProgressMonitor arg0, IAdaptable arg1) throws ExecutionException {
                                       EAnnotation annotation  = activity.getEAnnotation(ParticipantConstants.PARTICIPANT_ANNOTATION);
                                       if (annotation == null) {
                                               annotation = EcoreFactory.eINSTANCE.createEAnnotation();
                                               annotation.getDetails().put(ParticipantConstants.PARTICIPANT_NAME, "");
                                               annotation.getDetails().put(ParticipantConstants.PARTICIPANT_ROLE, "");
                                       annotation.getDetails().put(key, field.getText());
                                       return CommandResult.newOKCommandResult();
                               try {
                                       command.execute(new NullProgressMonitor(), null);
                               } catch (ExecutionException exception) {
                                       STPEclipseConPlugin.getDefault().getLog().log(new Status(IStatus.ERROR, STPEclipseConPlugin.PLUGIN_ID, IStatus.ERROR, exception.getMessage(), exception));

The trick is to create the EAnnotation if it doesn't exist yet.

The logical next step is to add the listener to the text fields as we initialize them in the createPartControl method.

nameText.addModifyListener(new ModifyParticipantInformation(ParticipantConstants.PARTICIPANT_NAME, nameText));
roleText.addModifyListener(new ModifyParticipantInformation(ParticipantConstants.PARTICIPANT_ROLE, roleText));

Showing your annotation on the diagram

Now, we want the annotation to appear on the diagram.

We need to implement the decorator extension point to do that.


The ParticipantDecorator class is implementing the IEAnnotationDecorator interface.

Create your own implementation of the decorator :

In the decorator, you will need to give the source of the EAnnotations the decorator will decorate:

       public String getAssociatedAnnotationSource() {
               return ParticipantConstants.PARTICIPANT_ANNOTATION;

You can choose where the decoration will appear on the shape (whatever constant defined by Direction is supported):

       public Direction getDirection(EditPart part, EModelElement elt, EAnnotation ann) {
              return Direction.SOUTH_EAST;

The decoration itself will be constituted into an image that you create in this method:

       public Image getImage(EditPart part, EModelElement element, EAnnotation annotation) {
               ImageDescriptor desc = STPEclipseConPlugin.imageDescriptorFromPlugin(STPEclipseConPlugin.PLUGIN_ID, "icons/participant.gif");
               return desc == null ? null : desc.createImage();

Finally you can show a IFigure object that will appear as the tooltip of the decoration.

We choose to show a simple label, we could do something more complicated.

      public IFigure getToolTip(EditPart part, EModelElement element, EAnnotation annotation) {
               String name = (String) annotation.getDetails(). get(ParticipantConstants.PARTICIPANT_NAME);
               String role = (String) annotation.getDetails(). get(ParticipantConstants.PARTICIPANT_ROLE);
               return new Label("Performed by " + name + " (" + role + ")");

Adding an annotation through a drag and drop action

We want to have some more interaction now, and the best way to do that for the end-user is to do some drag and drop on the diagram.

We are going to use a Participant view that will be complete enough to represent some participants. We will see how to drop them on the diagram just next.

The participant view

Back to the top