EAI 1.0 MAILINGLIST Avatar
  1. OMG Issue

EAI — The constraint on the parameters of an EAIMessageOperation

  • Key: EAI-56
  • Legacy Issue Number: 4876
  • Status: closed  
  • Source: Model Driven Solutions ( Ed Seidewitz)
  • Summary:

    Document: UML Profile and Interchange Models for EAI
    Section: 6.3.5 (EAIMessageOperation)

    Description:
    The text under Constraints in Section 6.3.5 states that a parameter of an EAIMessageOperation must have "a 1:1 relationship with EAIMessageContent or a subclass of EAIMessageContent." I assume that this is intended to mean a "1..1" assocation, since a "1:1" (usually read "1 to 1") relationship would require EVERY EAIMessageContent instance to be associated with some EAIParameter, as well as the converse, that every EAIParameter is associated with some EAIMessageContent instance (which, I think, is all that is intended). However, in this case, the constraint is already covered by the 1..1 multiplicity shown on the "message" association from EAIParameter to EAIMessageContent in Figure 6-9, and no other constraint on the association is needed.

    Recommendation:
    The constraint should read simply "Every input and output of an EAIMessageOperation is an EAIParameter." The corresponding OCL is:

    self.inputs->union(self.outputs)->forAll(oclIsType(EAIParameter))

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

    see below

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