Issue 4939: Hard/soft deletion actions.                                                                                                                                                                             (action-semantics-ftf)
Source: Ceira Technologies, Inc. (Mr. Michael Allen Latta, mlatta@ceira.com mlatta@cogility.com)
Nature: Uncategorized Issue
Severity: 
Summary: [Michael Latta?] Deletion action should have option for executing or not
executing the state machine exit actions, for example.

Resolution: Decline with clarification
Revised Text: 
Actions taken:
March 5, 2002: received issue
December 11, 2002: closed issue
Discussion: 
Model with exit transition from top state.  Sending this will cause the
exit actions to run.

Clarify that DestroyObjectAction does not cause execution of procedures
in the object, including the state machine procedures.  It interrupts
the RTC step, and does not treat destruction as an event.  Procedures
running in the object (methods, state machine actions) are stopped when
the object is deleted.  Soft abort can be achieved by sending an event
for a transition out of a state containing all the substates of the top
state.

End of Annotations:=====
Summary: Hard/soft deletion actions.

Text: 

[Michael Latta?] Deletion action should have option for executing or
not
executing the state machine exit actions, for example.


From: "Rumbaugh, James" <rumbaugh@rational.com>
To: conrad.bock@kabira.com, ActionFTF <action-semantics-ftf@omg.org>
Subject: RE: Draft Action FTF ballot, #3
Date: Fri, 29 Mar 2002 09:13:26 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: !/P!!/h2!!D>!!!:=\d9

See comments below on some items:


> 
>
**********************************************************************
> 
> VOTE (YES|NO|ABSTAIN):
> 
> Issue 4939: Hard/soft deletion actions.
>   http://cgi.omg.org/issues/issue4939.txt
> 
>   Resolution: Decline with clarification
> 
>   Discussion:
> 
>     Model with exit transition from top state.  Sending this 
> will cause the
>     exit actions to run.
> 
>     Clarify that DeleteObjectAction does not cause execution of the
>     procedures in the object, including the state machine 
> procedures.  It
>     interrupts RTC step, and does not treat deletion as an event.
>     Procedures running in the object (methods, state machine 
> actions) are
>     stopped when the object is deleted.
> 

It might help to point out that normally the compiler or tool would
generate
the code
to first force the state machine to exit to the outermost state and
then
would
destroy the object when all of its context is quiescent.

Typo: It is DestroyObjectAction, not DeleteObjectAction.