Issue 11662: Section: 11.2.1 (data reception) (marte-ftf) Source: Commissariat a l Energie Atomique-CEA (Dr. Arnaud Cuccuru, arnaud.cuccuru(at)cea.fr) Nature: Uncategorized Issue Severity: Significant 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)? Resolution: Disposition: See issue 11840 for disposition Revised Text: Actions taken: November 20, 2007: received issue February 17, 2010: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 20 Nov 2007 09:56:43 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Arnaud Cuccuru Company: Commissariat a l Energie Atomique - CEA/LIST mailFrom: arnaud.cuccuru@cea.fr Notification: Yes Specification: A UML Profile for MARTE Section: 11.2.1 FormalNumber: ptc/07-08-04 Version: Beta 1 RevisionDate: 04/08/07 Page: 120 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1) Gecko/20061010 Firefox/2.0 Description 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)?