Issue 6486: Clarify termination of asynchronous invocations (uml2-superstructure-ftf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Minor
Summary: Clarify that asychronously invoked behaviors/operations aren't
terminated by activity final
Resolution: see above
Revised Text: 
Actions taken:
November 7, 2003: received issue
March 8, 2005: closed issue
Discussion: 
In the Semantics section of ActivityFinalNode, p 298, in the first paragraph, add this after
the first sentence:
"Any behaviors invoked asynchronously by the activity are not affected."
End of Annotations:=====
me: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.gov
Nature: Revision
Severity: Minor
Subject: Clarify termination of asynchronous invocations


Clarify that asychronously invoked behaviors/operations aren't
Issue 6486: Clarify termination of asynchronous invocations             Activities
Conrad B
http://www.omg.org/issues/issue6486.txt
yourdirectory/uml2-superstructure-ftf.open.html#Issue6486


In the Semantics section of ActivityFinalNode, p 298, in the first
paragraph, add this after the first sentence:


  "Any behaviors invoked asynchronously by the activity are not affected."
:wq
terminated by activity final.