-
Key: EAI-26
-
Legacy Issue Number: 4963
-
Status: closed
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
Document: UML Profile and Interchange Models for EAI
Section: 6.4.1.3 (EAIPostDater)Description:
Section 6.4.1.3 states that an "EAIPostDater" holds a message in its buffer "until its individual timing condition is met". Does this mean that, at the appropriate time, the EAIPostDater autonomously emits the message, with no other stimulus, or that the operator checks the timing conditions each time it receives an incoming message? Also, as a child of EAIStream, EAIPostDater inherits the "emissionCondition" of a stream. How does this effect the behavior of the EAIPostDater?Recommendation:
Define the semantics of EAIPostDater to be the following:When a message is received on the input terminal, an EAIPostDater acts like an EAIStream in placing the message in its buffer and, possibly, immediately emitting a message. In addition, if the new incoming message is not the one that is immediately emitted, the EAIPostDater evaluates the timerMapping to create a timing condition for the message. Further, whenever any timing condition is met for any message in the buffer, the EAIPostDater autonomously places that message on its output terminal.
(An alternative would be to have EAIPostDater NOT be a child of EAIStream, with its semantics defined in a stand-alone fashion without an emission condition.)
-
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