Static Routing Slip

Overview

The static routing slip pattern in the EIP service engine is used to route an InOut message exchange through a series of endpoints.

Example EIP route

The following example shows how to define a static routing slip using the EIP service engine. Incoming messages pass through each of the endpoints, test:procA, test:procB, and test:procC, where the output of each endpoint is connected to the input of the next endpoint in the chain. The final endpoint, tets:procC, sends its output (Out message) back to the caller.

<eip:static-routing-slip service="test:routingSlip" endpoint="endpoint">
  <eip:targets>
    <eip:exchange-target service="test:procA" />
    <eip:exchange-target service="test:procB" />
    <eip:exchange-target service="test:procC" />
  </eip:targets>
</eip:static-routing-slip>

Attributes for Static Routing Slip

The following table lists attributes of eip:static-routing-slip:

Table 2.22. Attributes for Static Routing Slip

Attribute	Type	Description
`endpoint`	`xs:string`	Name of the endpoint.
`interfaceName`	`xs:QName`	QName of the interface exposed by the endpoint.
`service`	`xs:QName`	QName of the service exposed by the endpoint.
`wsdlResource`	`xs:string`	Spring resource used to load WSDL describing this endpoint (takes precedence over wsdlExchangeTarget).

Elements for Static Routing Slip

The following table lists elements of eip:static-routing-slip:

Table 2.23. Elements for Static Routing Slip

Element	Type	Description
`lockManager`	`spring:bean`	Lock manager to use for this endpoint. If you do not specify one, a default implementation is provided.
`store`	`spring:bean`	Store to use. If you do not specify one, the active storeFactory creates one.
`storeFactory`	`spring:bean`	Store factory used to create a store. If you do not specify one, a default factory is used, which creates in-memory only stores.
`targets`	(exchange-target)*	List of target endpoints used in the RoutingSlip
`timerManager`	`spring:bean`	Timer manager to use for this endpoint. If you do not specify one, a default implementation is used.
`wsdlExchangeTarget`	`exchange-target`	JBI endpoint acting as a WSDL proxy for this endpoint, enabling you to reuse WSDL across multiple endpoints.