UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — No ObjectEvent corresponding to SendObjectAction

  • Key: UML22-194
  • Legacy Issue Number: 9403
  • Status: closed  
  • Source: International Business Machines ( Jim Amsden)
  • Summary:

    SendObjectAction sends the object on its request InputPin the object at its target InputPin.

    AcceptEventAction can have a trigger that is a SignalEvent or CallEvent, but there is no Event type for ObjectEvent to represent the receipt of an object from a SendObjectAction. SignalEvent cannot be the trigger because it is not a Class and is not general enough.

  • Reported: UML 2.0 — Tue, 28 Feb 2006 05:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    Discussion
    This issue is obsolete. The UML 2.5 specification, in subclause 16.3.3, under “Send Actions”, now includes the
    following text in the description of the semantics of SendObjectAction: “If the object [sent by the action] is a Signal
    instance, then it may be handled by the target object in the same way as an instance sent from a SendSignalAction
    or BroadcastSignalAction. Otherwise, the reception of the object can only be handled using an AnyReceiveEvent (as
    described under Message Events in sub clause 13.3.3).”
    Disposition: Closed - No Change

  • Updated: Fri, 6 Mar 2015 20:58 GMT