EAI 1.0 MAILINGLIST Avatar
  1. OMG Issue

EAI — Insufficiency of the metamodel mapping for aggregators

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

    Document: UML Profile and Interchange Models for EAI
    Section: 8.3.12 (Aggregators)

    Description:
    The metemodel for EAIAggregator in Section 6.4.1.6 allows a DIFFERENT aggregateComplete and addToAggregate condition for EACH aggregate being formed. However, Section 8.3.12 only provides for the specification of a one aggregateComplete and one addToAggregate operation for the entire aggregator. (These operations take a specific aggregate as an argument, but the BEHAVIOR of the operation will be the same for all aggregates.)

    Recommendation:
    Define a new <<MessageAggregation>> stereotype. A class with this stereotype must have aggregateComplete and addToAggregate operations. Such a class maps to the EAIMessageAggregation metaclass (see Section 6.4.1.6). Require that a class with the stereotype <<Aggregator>> have associations with one or more <<MessageAggregation>> classes (note that multiple message aggregations can be achieved both by having an association with a multiplicity at the message aggregation end of greater than 1 or by having multiple associations with different message aggregation classes with different operator specifications).

    (Also change mapping constraints 20 an 21 in Section 8.6.2 to be consistent with this.)

  • Reported: EAI 1.0b1 — Tue, 23 Apr 2002 04:00 GMT
  • Disposition: Resolved — EAI 1.0
  • Disposition Summary:

    see above

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