-
Key: EAI-75
-
Legacy Issue Number: 4955
-
Status: closed
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
Document: UML Profile and Interchange Models for EAI
Section: 6.3.11.3.1 (EAIRequestFormat)Description:
Section 6.3.11.3.1 defines a "specifiedReplyTerminal" derived association (Figure 6-24) for an EAIRequestFormat that "...specifies a terminal to which replies should be sent." However, this information is not part of the specification of a request message, but it is part of the dynamic state of a request message, since it cannot be determined until that request message is actually created. As a metaclass, an instance of EAIRequestFormat is NOT a request message, but is rather a SPECIFICATION of a request message, and therefore should not include the state of the message itself.Recommendation:
Include the discussion of the identification of reply terminals as part of the semantics of an EAIRequestFormat, not the syntax. Remove the "specifiedReplyTerminal" -
Reported: EAI 1.0b1 — Thu, 7 Mar 2002 05:00 GMT
-
Disposition: Resolved — EAI 1.0
-
Disposition Summary:
see above
-
Updated: Fri, 6 Mar 2015 20:58 GMT
EAI — specifiedReplyTerminal association of EAIRequestFormat is dynamic state dat
- Key: EAI-75
- OMG Task Force: UML for EAI FTF