BPMN to BPEL mapping for End Events without Message Flows

You can generate BPEL code for BPMN End Events without Message Flows.

Pattern

BPMN comments

If there are no out going message flows attached to the End Event then the event can be ONLY be one of the following Trigger Types.

•exception

•compensation

•terminate

•none

BPEL comments

1 The End event Must be ONLY one of the following Trigger Types property which is determined from "BPMN Event".Stereotype

•exception

•compensation

•terminate

•none

2 If the stereotype is an "exception" then a <throw> element is created.

3 The qname of the faultName attribute value is taken from the BPMN Event definition property"BPMN Event". "Fault Name"

4 The ncname of the faultVariable attribute value is taken from the BPMN Event definition property "BPMN Event". "Fault Variable"

5 If the stereotype is an "compensation" then a <compensate> element is created

6 The ncname of the scope attribute value is taken from the BPMN Event definition property "BPMN Event". "Compensation"

7 If the stereotype is an "terminate" then a <terminate> element is created

8 If the stereotype is an "none" then no element is created since the end event then just marks the end of a path.

9 For all of the above End events the standard-attributes are determined from the Event symbol.

Element construct

<throw faultName="qname"

faultVariable="ncname"

standard-attributes>

</throw>

<compensate scope="ncname"

standard-attributes>

</compensate>

<terminate

standard-attributes>

</terminate>