-
Key: UML22-1198
-
Legacy Issue Number: 7006
-
Status: closed
-
Source: PostFinance ( Karl Guggisberg)
-
Summary:
Constraint on ControlNode (p. 317):
"[1] The edges coming into and out of a control node must be either all object flows or all control flows."
Semantics of JoinNode (p. 339):
"If there is a token offered on all incoming edges, then tokens are offered on the outgoing edge according to the following join rules: 1. If all the tokens offered on the incoming edges are control tokens, then one control token is offered on the outgoing edge. 2. If some of the tokens offered on the incoming edges are control tokens and other are data tokens, then only the data tokens are offered on the outgoing edge."
Item 2.) should be: "2. If all the tokens offered on the incoming edges are data tokens, then only the data tokens are offered on the outgoing edge."
-
Reported: UML 2.0 — Sun, 22 Feb 2004 05:00 GMT
-
Disposition: Resolved — UML 2.1
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 22:54 GMT
UML22 — Inconsistency between constraint of ControlNode and Semantics of JoinNode
- Key: UML22-1198
- OMG Task Force: UML 2.2 RTF