You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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-http 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:

Using servicemix-eip in a ServiceMix xml configuration file

TODO:

Patterns

Content-Based router

TODO:

Error formatting macro: snippet: java.lang.NullPointerException

Pipeline

TODO:

Error formatting macro: snippet: java.lang.NullPointerException

Static Recipient List

TODO:

Error formatting macro: snippet: java.lang.NullPointerException

Static Routing Slip

TODO:

Error formatting macro: snippet: java.lang.NullPointerException

Wire Tap

TODO:

Error formatting macro: snippet: java.lang.NullPointerException

XPath Splitter

TODO:

Error formatting macro: snippet: java.lang.NullPointerException
  • No labels