UML22 — No ObjectEvent corresponding to SendObjectAction

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.

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