doActivity timing: start on entry and let completion wait for it #700
Copy link
Copy link
Open
Labels
enhancementumlUML state machine semantics, tracked in #692UML state machine semantics, tracked in #692
Milestone
Description
Why
invoke is how this library runs a doActivity, and it is the most used way to run work while in a state. UML starts the doActivity as part of entering the state and fires the completion only after it ends; the SCXML default starts invocations at the end of the macrostep and fires eventless transitions immediately.
Scope
- A class-level flag for the start time of invocations (conflict K14 in the PSSM xfail map).
- Completion of a state with a running doActivity waits for it (K2), built on the explicit completion spelling.
- Defaults keep SCXML behavior.
Acceptance
PSSM cases coded conflict:K14 and conflict:K2 pass with the flag on both engines; W3C SCXML suite unchanged with defaults.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementumlUML state machine semantics, tracked in #692UML state machine semantics, tracked in #692
Activity