MARTE 1.0b2 FTF Avatar
  1. OMG Issue

MARTE — Section: 11.2.1 (data reception)

  • Key: MARTE-42
  • Legacy Issue Number: 11662
  • Status: closed  
  • Source: Commissariat a l Energie Atomique-CEA ( Arnaud Cuccuru)
  • Summary:

    The FlowSendAction concept is introduced to enable sending of data via a FlowPort. It seems that there is no equivalent concept (action) for data reception. If a given behavior has to be expressed according to data arriving from an input port, how is the behavior “notified” that a data is available on this port (I mean: is there something equivalent to AcceptCallAction used for service oriented communication schemes)? Once that the notification has occurred in one way or another, do we access to this data with something like a ReadStructuralFeatureAction (because ports are structural features)?

  • Reported: MARTE 1.0b1 — Tue, 20 Nov 2007 05:00 GMT
  • Disposition: Resolved — MARTE 1.0b2
  • Disposition Summary:

    Disposition: See issue 11840 for disposition

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