Activities can be used to implement the behaviour of nodes, in which case this behaviour is associated to a graphical node in the diagram, or they can be added as events, in that case, they are being hidden from the diagram.
If an activity is the node behaviour, then it can control the propagation of execution. Node behaviours can be external activities. That means their runtime behaviour is a wait state. In that case, {@link ExternalActivity} should be implemented to also handle the external triggers.
If an activity is being used as a listener to process events, the propagation of the execution can not be controlled in an activity. So following methods are not to be called during {@link Event}s.
If an exception is thrown that is not handled by an {@link ExceptionHandler}, the exception will be wrapped and propagated to the original client that performed an operation on the execution.
|
|
|
|
|
|
|
|