org.camunda.bpm.engine.impl.bpmn.behavior
Class BoundaryEventActivityBehavior
java.lang.Object
org.camunda.bpm.engine.impl.bpmn.behavior.FlowNodeActivityBehavior
org.camunda.bpm.engine.impl.bpmn.behavior.BoundaryEventActivityBehavior
- All Implemented Interfaces:
- CoreActivityBehavior<ActivityExecution>, ActivityBehavior, SignallableActivityBehavior
public class BoundaryEventActivityBehavior
- extends FlowNodeActivityBehavior
The BPMN Boundary Event.
The corresponding activity must either be
PvmActivity.isCancelScope() in case of an interrupting boundary event. In this case
the scope to which the boundary event is attached will already be cancelled when this behavior is executed.
PvmActivity.isConcurrent() in case of a non-interrupting boundary event. In this case
the new concurrent execution will already have been created when this behavior is executed.
As a result, the boundary event does noting "special". It will be left by all outgoing sequence flows
just like any other activity.
- Author:
- Daniel Meyer, Roman Smirnov
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
BoundaryEventActivityBehavior
public BoundaryEventActivityBehavior()
Copyright © 2014 camunda services GmbH. All rights reserved.