Issue 6106: Pin/parameter matching 4 (uml2-superstructure-ftf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary: Clarify in CallBehaviorAction and CallOperationAction that the operation
and behavior may have out or results and still be called asynchronously.
The constraints on these actions regarding pin/parameter matching only
applies in the synchronous case.


Resolution: see above
Revised Text: 
Actions taken:
August 30, 2003: received issue
March 8, 2005: closed issue
Discussion: 
In the Semantics section of CallBehaviorAction, p 225, in the paragraph labelled [3],
after the second sentence, add:
"Any return or out values from the invoked behavior are not passed back to the
containing activity."
In the Semantics section of CallOperationAction, p 228, in paragraph labelled [4], after
the first sentence, add:
"Any return or out values from the invoked operation are not passed back to the
containing activity."
End of Annotations:=====
Name: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.gov
Nature: Revision
Severity: Significant
Subject: Pin/parameter matching 4


Clarify in CallBehaviorAction and CallOperationAction that the operation
and behavior may have out or results and still be called asynchronously.
The constraints on these actions regarding pin/parameter matching only
Issue 6106: Pin/parameter matching 4            Activities      Conrad B.
http://www.omg.org/issues/issue6106.txt
yourdirectory/uml2-superstructure-ftf.open.html#Issue6106


Resolved


In the Semantics section of CallBehaviorAction, p 225, in the paragraph
labelled [3], after the second sentence, add:


  "Any return or out values from the invoked behavior are not passed back
   to the containing activity."


In the Semantics section of CallOperationAction, p 228, in paragraph
labelled [4], after the first sentence, add:


  "Any return or out values from the invoked operation are not passed
   back to the containing activity."
applies in the synchronous case.