-
Key: WFMF11-8
-
Legacy Issue Number: 3266
-
Status: open
-
Source: Hitachi ( Toshiaki Sakaguchi)
-
Summary:
The spec says in section 2.4.5 that the state of WfExecutionObject can be
{terminated, aborted} state only from open.running state. It
set to closed.
is inconvenient when the user makes WfProcess or WfActivity but wants to
remove the object for some reasons. (For example, the object is created by
mistake, the object cannot be started, etc.) We have to start the object to
terminate it, and if it cannot be started also, we cannot set its state to
closed state.
While Figure 2-2 appears to suggest the state change from any open state
to any closed state are possible. The transition to closed.completed state
should only be from open.running state and it should be distinguished
from closed.{terminated,aborted} state.
Resolution:
Add the transition from open.not_running.not_started to
closed.{terminated, aborted}state.
Correct Figure 2-2 so that we can clearly understand the transition to
closed.completed state is permitted only from open.running state. -
Reported: WfMF 1.1 — Tue, 1 Feb 2000 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:59 GMT