ActiveVOS Designer User’s Guide
In many cases, a BPMN element can be implemented as one or more BPEL activities, described in the tables below.
The following tables are divided into BPMN types: tasks, throw events, and catch events.
For additional implementations, see BPMN-to-BPEL Implementation of Gateways and Control Flow.
Tasks
|
BPMN Task |
BPEL Implementation(s) |
|---|---|
|
Service |
Invoke |
|
User |
People activity, task type |
|
Script |
Assign |
|
Rule |
Invoke |
|
Suspend |
Suspend |
|
Validate |
Validate |
|
Abstract |
Empty |
|
Manual |
|
|
Send |
|
|
Receive |
Receive |
Throw Events
|
BPMN Throw Event |
BPEL Implementation |
|---|---|
|
None/Start/End |
|
|
Message |
|
|
Error |
|
|
Compensate |
|
|
Terminate |
|
Catch Events
Any catch event can be dropped onto an activity’s boundary to create a boundary event, or into a scope (event subprocess) to create a handler.
|
BPMN Catch Event |
BPEL Implementation |
|---|---|
|
Timer |
|
|
Message |
|
|
Error |
|
|
Compensation |
Scope compensation handler |
|
Cancel |
Scope termination handler |
Copyright (c) 2004-2011 Active Endpoints, Inc.