-
Key: UCM11-18
-
Status: closed
-
Source: THALES ( Thomas Vergnaud)
-
Summary:
Standard library model core.xml contains the following declaration:
<interface name="message_intf"> <method name="push"> <param dir="in" name="message" type="message_type_t"/> <param dir="return" name="ecode" type="::core::return_codes::comm_ecode"/> </method> </interface>
and
<portType name="msg_emtr_pt"> <portElement interface="api::message_intf" kind="required" name="emtr_pe"/> </portType> <portType name="msg_rcvr_pt"> <portElement interface="api::message_intf" kind="provided" name="rcvr_pe"/> </portType>
This indicates that message emitter and message receiver port types rely on the same interface message_intf. This interface has a unique method push with a return type for error codes. The error code makes sense for the emitter, as it let it know wether the communication has been successful or not. But it makes no sense for the receiver: the value of the error code must be set by the connector, not the receiving component.
There is a similar problem with the request-reponse connector.
-
Reported: UCM 1.0 — Mon, 9 Apr 2018 13:58 GMT
-
Disposition: Resolved — UCM 1.1
-
Disposition Summary:
remove return codes for data reception interfaces
create separate interfaces for data emitter and data receiver for message and request-response interactions
-
Updated: Wed, 3 Oct 2018 14:18 GMT
-
Attachments:
- ucm_core-messages.xml 1 kB (application/xml)
- ucm_ext_interac-req_resp.xml 4 kB (application/xml)
UCM11 — there should be no returned error code for data consumers in the standard library
- Key: UCM11-18
- OMG Task Force: UCM 1.1 RTF