servicemix-eip
The servicemix-eip component is a routing container where different routing patterns can be deployed as service unit.
This component is based on the great Enterprise Integration Patterns book.
Supported patterns:
- Content-Based Router
- Pipeline
- Static Recipient List
- Static Routing Slip
- Wire Tap
- XPath Splitter
In addition, this component can use all ServiceMix flows (including clustered and transactional flows), can be configured to be resilient to crashes and supports full fail-over to another node when clustered.
Using servicemix-eip as a standard JBI component
Installation
Installing the servicemix-eip component can be done in several ways:
- drop the installer zip in an hotdeploy directory monitored by ServiceMix
- using ant tasks
Note that when using ant tasks, the component is not started, you will have to start it manually using ant tasks or a console.
Configuration
TODO: configure a persistent / clustered store
Service Unit packaging
TODO:
Content of xbean.xml file to be packaged as a SU
<beans xmlns:eip="http://servicemix.apache.org/eip/1.0"> ... add eip patterns here ... </beans>
Using servicemix-eip in a ServiceMix xml configuration file
TODO:
<beans xmlns:sm="http://servicemix.apache.org/config/1.0" xmlns:eip="http://servicemix.apache.org/eip/1.0"> <sm:container ...> <sm:activationSpecs> <sm:activationSpec> <sm:component> <eip:component> <eip:endpoints> ... add eip patterns here ... </eip:endpoints> </eip:component> </sm:component> </sm:activationSpec> ... </sm:activationSpecs> </sm:container> ... </beans>
Patterns
Content-Based router
TODO:
Pipeline
TODO:
Static Recipient List
TODO:
Static Routing Slip
TODO:
Wire Tap
TODO:
XPath Splitter
TODO: