EAI 1.0 NO IDEA Avatar
  1. OMG Issue

EAI — Missing derivation of the "promotedTerminal" association

  • Key: EAI-20
  • Legacy Issue Number: 4897
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    Document: UML Profile and Interchange Models for EAI
    Section: ('Exposing' terminals in an EAIMessageFlow)

    The meaning of the derived "promotedTerminal" association is discussed in Section, but no clear derivation constraint is given.

    Given the FCM metmamodel (see Figure 6-2), the appropriate constraint is not so easy to formulate. I think the following will do, as a constraint on EAICompoundOperator (NOT EAITerminal).

    The output terminal of each EAISource in the implementingComposition of an EAICompoundOperator is promoted to the input terminal of the EAICompoundOperator that represents the same EAIParameter (of the FCMOperation implemented by the EAISource) as the output terminal of the EAISource.

    let sourceTerminals =
    self.implementingComposition.nodes->select(oclIsType(EAISource)).interface in
    self.interface->select(terminalKind = #in)
    ->includesAll(sourceTerminals.promotedTerminal) and
    and parameter = promotedTerminal.parameter)

    (This assumes that there is already a constraint requiring an EAISource to have output terminals that represent the input parameters of the operation it implements.)

  • Reported: EAI 1.0b1 — Fri, 22 Feb 2002 05:00 GMT
  • Disposition: Resolved — EAI 1.0
  • Disposition Summary:

    see above

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