-
Key: UML22-114
-
Legacy Issue Number: 8760
-
Status: closed
-
Source: Dassault Systemes ( Mr. Nerijus Jankevicius)
-
Summary:
MessageEnd are MessageOccurrenceSpecification that redefines "event"
> as MessageEvent.
> DestructionEvent and CreationEvent are not subclasses of
> MessageEvent, so can't be on message end, so how to map "create
> message" and "destroy message"?This is an open item. The one thing that was highly contested in the FTF was that there be explicit create and destroy messages. So, they are no longer in MessageKind.
> Also unclear how to map Reply
> message, what kind of events should be in reply message ends?You should check with Oystein.
> Events are owned by package, it's very uncomfortable (at least two
> nesting levels from Interaction), it think they should be owned by
> Interaction.No, because the whole idea of events is that they have to be shared by the sender's and reciever's behaviors. It makes little sense to define them in an Interaction.
-
Reported: UML 1.4.2 — Tue, 3 May 2005 04:00 GMT
-
Disposition: Resolved — UML 2.2
-
Disposition Summary:
See issue 14629 for disposition
-
Updated: Fri, 6 Mar 2015 20:58 GMT