EAI 1.0 MAILINGLIST Avatar
  1. OMG Issue

EAI — Missing specification of a table to hold EAIMessageTimerConditions

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

    Document: UML Profile and Interchange Models for EAI
    Sections: 6.4.1.10.1 (EAITimeSetOperator) and 6.4.1.10.2 (EAITimeCheckOperator)

    Description:
    Figure 6-42 in Section 6.4.1.10.1 and Figure 6-45 in Section 6.4.1.10.2 show the individual associations from EAITimeSetOperator and EAITimeCheckOperator to EAIMessageTimerCondition. Not only does this define dynamic state rather than metadata, it defines DIFFERENT dynamic states for the two operators, rather than the single shared table that is necessary.

    Recommendation:
    Remove the "timeSetConditions" association (between EAITimeSetOperator and EAIMessageTimerCondition) and "timeCheckConditions" association (between EAITimeCheckOperator and EAIMessageTimerCondition) from Figures 6-42 and 6-45. Instead, define an EAITimerConditionTable class as a child of EAIResource and put constraints on EAITimeSetOperator and EAITimeCheckOperator that each has a exactly one resource, which is and EAITimerConditionTable.

  • Reported: EAI 1.0b1 — Thu, 7 Mar 2002 05:00 GMT
  • Disposition: Resolved — EAI 1.0
  • Disposition Summary:

    se above

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