-
Key: UML25-393
-
Legacy Issue Number: 18013
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
Detail:
Explain how the exception works with the other out parameter.
Should Accepted Computers also be streaming?
If not, under what circumstances are the AcceptedComputers released?
Without an exception, how would this stop?
Does the AcceptedComputers only release when rejectedcomputers is raised and handled; otherwise when would it be released? -
Reported: UML 2.4.1 — Thu, 27 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
This example is problematic a couple of ways. First, the fact that the input parameter is streaming would,
indeed, seem to indicate that the outputs should be streaming. However, it is not allowed for a parameter to
be both isStream and isException (constraint Parameter::stream_and_exception). Second, the description of
example implies that computers are sorted into rejected and accepted. However, in Subclause 15.2.3 it states
“An output posted to an exception Parameter precludes outputs from being posted to other output Parameters
of a Behavior.” So having any rejected computers would preclude having any accepted computers.
The intent of the examples in Subclause 15.4.5 are simply to illustrate the use of ActivityParameterNodes,
including for streaming and exception Parameters. However, the examples should do this in a way that
makes sense. -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Location: Figure 15.57 page 426
- Key: UML25-393
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF