-
Key: UML22-368
-
Legacy Issue Number: 12218
-
Status: closed
-
Source: oose Innovative Informatik eG ( Mr. Axel Scheithauer)
-
Summary:
This paragraph refers to signal and change events, but should refer to signal and call events: >>However, relative to its use for signal events (see “SignalEvent (from Communications)” on page 449) and change events (see “ChangeEvent (from Communications)” on page 435), the <assignment-specification> ... Instead it should read: >>However, relative to its use for signal events (see “SignalEvent (from Communications)” on page 449) and call events (see “CallEvent (from Communications)” on page 434), the <assignment-specification> ... ChangeEvents don't even have an assignment specification, but signal an call events do.
-
Reported: UML 2.1.2 — Fri, 8 Feb 2008 05:00 GMT
-
Disposition: Resolved — UML 2.2
-
Disposition Summary:
This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
Disposition: Closed - No Change -
Updated: Fri, 6 Mar 2015 20:58 GMT
UML22 — 15.3.14: This paragraph refers to signal and change events
- Key: UML22-368
- OMG Task Force: UML 2.2 RTF