-
Key: EAI-37
-
Legacy Issue Number: 5230
-
Status: closed
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
Document: UML Profile and Interchange Models for EAI
Section: 8.3.5 (Post Daters)Description:
In the Section 6.4.1.3, the timing condition for a message received by an EAIPostDater is described as possibly entailing "a derivation from the content of the input message by a 'timerMapping'." This seems to indicate that a "timerMapping" is a mapping from a message (or message content) to a timing condition. However, while the "setTimingCondition" operation, which reflects the timerMapping, specified for a Post Dater class in Section 8.3.5 has a message content argument, it produces no result.Recommendation:
To correctly reflect the timerMapping, it would seem that the setTimingCondition operation should instead be "createTimingCondition", returning a TimingCondition. A model could also include a specification of exactly what a TimingCondition is, if this is necessary for precision of specification (though this would not be mapped to the metamodel, except as part of the specification of the FCMMapping that is the timerMapping). -
Reported: EAI 1.0b1 — Thu, 18 Apr 2002 04:00 GMT
-
Disposition: Resolved — EAI 1.0
-
Disposition Summary:
see above
-
Updated: Fri, 6 Mar 2015 20:58 GMT
EAI — The mapping of the setTimingCondition opeation of a Post Dater
- Key: EAI-37
- OMG Task Force: UML for EAI FTF