A recipient list, shown in Figure A.6, is a type of router that sends each incoming message to multiple different destinations. The ServiceMix EIP recipient list is restricted to processing InOnly and RobustInOnly exchange patterns. Moreover, the list of recipients must be static. This pattern maps to the recipient list with fixed destination pattern in Fuse Mediation Router.

Figure A.6. Static Recipient List Pattern

Example A.16 shows how to define a static recipient list using the ServiceMix EIP component. Incoming messages are copied to the test:messageFilter endpoint and to the test:trace4 endpoint.

<eip:static-recipient-list service="test:recipients"
                           endpoint="endpoint">
  <eip:recipients>
    <eip:exchange-target service="test:messageFilter" />
    <eip:exchange-target service="test:trace4" />
  </eip:recipients>
</eip:static-recipient-list>

Example A.17 shows how to define an equivalent route using Fuse Mediation Router XML configuration.

<route>
  <from uri="jbi:endpoint:http://progress.com/demos/test/recipients/endpoint"/>
  <to uri="jbi:service:http://progress.com/demos/test/messageFilter"/>
  <to uri="jbi:service:http://progress.com/demos/test/trace4"/>
</route>

	Note
	The preceding route configuration appears to have the same syntax as a Fuse Mediation Router pipeline pattern. The key difference is that the preceding route is intended for processing InOnly message exchanges, which are processed in a different way. See Pipes and Filters for more details.

Example A.18 shows how to define an equivalent route using the Fuse Mediation Router Java DSL.

from("jbi:endpoint:http://progress.com/demos/test/recipients/endpoint").
    to("jbi:service:http://progress.com/demos/test/messageFilter", "jbi:service:http://progress.com/demos/test/trace4");