FUML12 — Problem with ActivityExecution::terminate

Specification: Semantics of a Foundational Subset for Executable UML Models (fUML), v1.1, RTF Beta (ptc/2012-10-18)

Subclauses: 8.5.2.2.2 ActivityExecution

The ActivityExecution::terminate operation calls terminateAll on the activationGroup for the activity execution. However, the activationGroup attribute is not set unless the execute operation has been called. If an activity is started asynchronously, then it will be instantiated as an activity execution within a classifier behavior execution, but, since this execution is asynchronous to the invoker of the activity, it is possible for the invoker to destroy (and so terminate) the activity instance before the activity execution is actually executed. That is, it is, in fact, possible for the terminate operation to be called on an activity execution without the execute operation ever having been called.

In order to avoid a possible error, the terminate operation should check that the activationGroup is not null before calling terminateAll on it.

Update ActivityExecution::terminate

Agreed.