SoaML 1.1 RTF Avatar
  1. OMG Issue

SOAML11 — Figure 95 uses UML ports without UML semantics

  • Key: SOAML11-73
  • Legacy Issue Number: 14924
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Figure 95 isn't explained very well, but from other conversations it
    seems to assume partitions representing ports have (references to)
    external objects as runtime values, where the external objects are the
    ones at the other end of the connector coming into the port from
    outside. This is assumed so the invocation actions can send these
    external objects operation calls based on the partitions they are in (
    the partitions represent port properties, which means the runtime value
    of the ports must be the runtime input values of invocation actions in
    the partition).

    However, ports are composite properties, see constraint [2] on ports,
    which means external objects that are values of ports would be deleted
    with when the runtime owner of the port is. For example, deleting a
    buyer object would delete the seller object at runtime. In addition,
    it would be a very rare user of UML that would assume an externally
    connected port connector had as its value the object at the other end
    of the connector. This is very far from UML, with significant
    unintended consequences.

    soaML could define an extension of UML for port partitions to give the
    semantics of InvocationAction:onPort with input pin targeting "self".
    Then the operation calls would go through the port represented by the
    partition to the external object.

  • Reported: SoaML 1.0b1 — Wed, 6 Jan 2010 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT