-
Key: UML22-1020
-
Legacy Issue Number: 9007
-
Status: closed
-
Source: NIST ( Mr. Conrad Bock)
-
Summary:
In Description section of Common Behaviors, CallConcurrencyKind, how can "Multiple invocations of a behavioral feature" occuring simultaneously have a "first behavioral feature". Full text: "Multiple invocations of a behavioral feature may occur simultaneously to one instance, but only one is allowed to commence. The others are blocked until the performance of the first behavioral feature is complete. It is the responsibility of the system designer to ensure that deadlocks do not occur due to simultaneous blocks."
-
Reported: UML 2.0 — Sun, 25 Sep 2005 04:00 GMT
-
Disposition: Resolved — UML 2.1.2
-
Disposition Summary:
While nit-picking, the issue submitter is correct
-
Updated: Fri, 6 Mar 2015 20:58 GMT