Issue 6396: UML 2 super / state machines / entry and exit actions cannot be redefined (uml2-superstructure-ftf)
Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org)
Nature: Uncategorized Issue
Severity: 
Summary: In the current metamodel it does not appear as if state entry and exit actions can be redefined. Since transition actions can be redefined, this restriction does not make sense and should probably be removed. 

Resolution: 
Revised Text: 
Actions taken:
October 31, 2003: received issue
March 8, 2005: closed issue
Discussion: 
To be precise, actions on transitions are not redefined, but replaced. It is the transition
which is being redefined. Practically it allows the overriding of transition actions.
A similar approach should be taken for state actions and “doActivity” actions. Therefore,
the redefinition text for states on page 481 should be modified from:
“A simple state can be redefined (extended) to become a composite state (by adding a region) and a
composite state can be redefined (extended) by adding regions and by adding vertices, states,
entry/exit/do activities (if the general state has none), and transitions to inherited regions.”
To:
A simple state can be redefined (extended) to become a composite state (by adding a region) and a
composite state can be redefined (extended) by adding regions and by adding vertices, states, and
transitions to inherited regions. All states may add or replace entry, exit, and “doActivity” actions.
End of Annotations:=====
ubject: UML 2 super / state machines / entry and exit actions cannot be redefined 
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 
From: Branislav Selic <bselic@ca.ibm.com> 
Date: Fri, 31 Oct 2003 20:07:57 -0500 
X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 6.0.2CF1|June 9, 2003) at 
 10/31/2003 20:07:58, 
        Serialize complete at 10/31/2003 20:07:58 


In the current metamodel it does not appear as if state entry and exit actions can be redefined. Since transition actions can be redefined, this restriction does not make sense and should probably be removed. 

Bran Selic
IBM Software Group -- Rational Software
770 Palladium Drive
Kanata, Ontario, Canada
K2V 1C8

ph. (613) 591-7915
fax (613) 599-3912

OMG Issue 6396
Title: entry and exit actions cannot be redefined
Source: International Business Machines (Mr. Bran Selic, mailto:%20bselic@ca.ibm.com)
 Summary: 
In the current metamodel it does not appear as if state entry and exit actions can be redefined. Since transition actions can be redefined, this restriction does not make sense and should probably be removed. 

Discussion: 
To be precise actions on transitions are not redefined, but replaced. It is the transition which is being redefined. Practically it allows 
To .override. the actions.
A similar approach should be taken for state actions and .doActivity. actions. Therefore, the redefinition text for states should be modified from:

.A simple state can be redefined (extended) to
become a composite state (by adding a region) and a composite state can be redefined (extended) by adding regions and
by adding vertices, states, entry/exit/do activities (if the general state has none), and transitions to inherited regions..

To:

A simple state can be redefined (extended) to
become a composite state (by adding a region) and a composite state can be redefined (extended) by adding regions and
by adding vertices, states, and transitions to inherited regions. All states may add or replace entry, exit, and .doActivity. actions.

Disposition: Resolved.
:wq

e-mail: bselic@ca.ibm.com