UCM 1.0 FTF — Open Issues - OMG Issue Tracker

Key: UCM-50

Status: closed

Source: THALES ( Thomas Vergnaud)

Summary:

UCM component bodies are supposed to have a method named on_startup() that takes a list of ports to connect as parameter. When creating a statically typed API (with an explicit list of PortElement), one has to decide which order to follow for the ports. For example, for a component C that has two port elements peA and peB, should we have on_startup(peA a, peB b) or on_startup(peB b, peA a) ?
The standard cannot leaves this choice implementation-dependent, as it would prevent code portability.
Also, port elements have two relationships named "executor", which is confusing.

Reported: UCM 1.0b1 — Tue, 21 Mar 2017 17:21 GMT

Disposition: Resolved — UCM 1.0

Disposition Summary:

Connect port elements using on_connect instead of on_startup

Simplify the programming model by manking the Connectable interface mandatory, and remove parameters of method on_startup().
This makes implementation work more portable.
Also update the programming model diagrams to use SVG instead of PNG images.

Updated: Mon, 16 Oct 2017 15:14 GMT

Attachments:

ucm.idl 2 kB ()
ucm_component_interfaces.svg 14 kB (image/svg+xml)
ucm_container_interfaces.svg 10 kB (image/svg+xml)
ucm_container_programming_model.svg 15 kB (image/svg+xml)
ucm_lifecycle.svg 41 kB (image/svg+xml)