-
Key: UML22-120
-
Legacy Issue Number: 8785
-
Status: closed
-
Source: Dassault Systemes ( Mr. Nerijus Jankevicius)
-
Summary:
How return message should be mapped into model? What kind of events are on message ends, how return values should be mapped? Should return values be arguments of message? How return message can be recognized in the model?
How variable assignment should be mapped and related with message? -
Reported: UML 1.4.2 — Wed, 18 May 2005 04:00 GMT
-
Disposition: Resolved — UML 2.2
-
Disposition Summary:
There has never been anything called a "return message", but the issue is probably about "reply message" which we had forgotten to give a messageSort, but that has been fixed. The other issues are related, but are also asking for clarification of metamodel encoding. This should eventually be picked up again if necessary during a major revision.
Disposition: ClosedOutOfScope -
Updated: Fri, 6 Mar 2015 20:58 GMT