Legacy Issue Number: 4969
Source: Model Driven Solutions ( Ed Seidewitz)
Document: UML Profile and Interchange Models for EAI
Section: 18.104.22.168.1 (EAIRouterUpdate and EAIBroadcaster)
From the point of view of an EAIRouterUpdate, the "routingTargets" association on its EAIRoutingTable, as shown in Figure 6-33 in Section 22.214.171.124.1, is dynamic state and therefore not appropriate for a metamodel. From the point of view of an EAIBroadcaster, the "routingTargets" of its EAIRoutingTable may also be dynamic state (if added by an EAIRouterUpdate). However, it is also desirable to be able to statically specify, in the message-flow model, the connection of EAILinks to an EAIBroadcaster. Since an EAIBroadcaster is defined to have its own output terminal, one would assume that these static EAILinks would be connected to it. Do the terminals so connected also need to be statically specified in the EAIRoutingTable? This would be the only reason to keep the "routingTargets" association in the metamodel.
Remove the "routingTargets" association from Figure 6-33. Further, make EAIRoutingTable a child of EAIResource and remove both the "routingTable" association (between EAIRouterUpdate and EAIRoutingTable) and the currentRoutingTable association (between EAIBroadcaster and EAIRoutingTable), instead adding the constraints that EAIRouterUpdate and EAIBroadcaster each have exactly one resource, which is an EAIRoutingTable.
The semantics for EAIRouterUpdate remains essentially unchanged. Define the semantics for EAIBroadcaster as follows:
The target terminals of any EAILinks connected to the output terminal of an EAIBroadcaster are added to the EAIRoutingTable for that EAIBroadcaster as the initial set of routing targets. This set may be changed by the operation of an EAIRouterUpdate operator. When a message is received on the input terminal of an EAIBroadcaster, dynamic EAILinks are established between the output terminal of the EAIBroadcaster and each of the terminals in the current set of routing targets of the EAIRoutingTable of the EAIBroadcaster. The input message is then copied to the output terminal and thus sent to each of the routing targets.
Reported: EAI 1.0b1 — Thu, 7 Mar 2002 05:00 GMT
Disposition: Resolved — EAI 1.0
Updated: Fri, 6 Mar 2015 20:58 GMT