-
Key: EAI-27
-
Legacy Issue Number: 4964
-
Status: closed
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
Inclusion of the dynamic state "buffer" and "timingCondition" in the metamodel for EAIPostDater
Document: UML Profile and Interchange Models for EAI
Section: 6.4.1.3 (EAIPostDater)Description:
Figure 6-28 in Section 6.4.1.3 shows "buffer" and "timingCondition" associations on EAIPostDater. However, this is part of the dynamic state of an EAI post-dater operator, not part of the specification of the operator. An instance of EAIPostDater is a SPECIFICATION of an EAI post-dater operator, not the operator itself, and therefore should not include the dynamic state of the operator.Recommendation:
Remove the "buffer" and "timingCondition" associations from Figure 6-28. -
Reported: EAI 1.0b1 — Thu, 7 Mar 2002 05:00 GMT
-
Disposition: Resolved — EAI 1.0
-
Disposition Summary:
see below
-
Updated: Fri, 6 Mar 2015 20:58 GMT
EAI — Inclusion of dynamic state "buffer" and "timingCondition" in metamodel for
- Key: EAI-27
- OMG Task Force: UML for EAI FTF