Page History

...

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

...

Content-Based router

TODO:
ContentBasedRouter can be used for all kind of content-based routing.
This pattern implements the Content-Based Router pattern.

{snippet:id=content-based-router|lang=xml|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-eip/src/test/resources/org/apache/servicemix/eip/spring.xml}

Pipeline

TODO:
The Pipeline component is a bridge between an In-Only (or Robust-In-Only) MEP and an In-Out MEP. When the Pipeline receives an In-Only MEP, it will send the input in an In-Out MEP to the tranformer destination and forward the response in an In-Only MEP to the target destination.

The old org.apache.servicemix.components.util.PipelineComponent will be deprecated. This one offers the same feature but can be safely clustered and use in a transactional enviromnent.

{snippet:id=pipeline|lang=xml|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-eip/src/test/resources/org/apache/servicemix/eip/spring.xml}

Static Recipient List

TODO:
The StaticRecipientList component will forward an input In-Only or Robust-In-Only exchange to a list of known recipients.
This component implements the Recipient List pattern, with the limitation that the recipient list is static.

{snippet:id=static-recipient-list|lang=xml|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-eip/src/test/resources/org/apache/servicemix/eip/spring.xml}

Static Routing Slip

TODO:
A RoutingSlip component can be used to route an incoming In-Out exchange through a series of target services.
This component implements the Routing Slip pattern, with the limitation that the routing table is static.
This component only uses In-Out MEPs and errors or faults sent by targets are reported back to the consumer, thus interrupting the routing process.

{snippet:id=static-routing-slip|lang=xml|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-eip/src/test/resources/org/apache/servicemix/eip/spring.xml}

Wire Tap

TODO:
A WireTap component can be used to forward a copy of the input message to a listener.
This component implements the WireTap pattern.
It can handle all 4 standard MEPs, but will only send an In-Only MEP to the listener.

{snippet:id=wire-tap|lang=xml|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-eip/src/test/resources/org/apache/servicemix/eip/spring.xml}

XPath Splitter

TODO:
The XPathSplitter component implements the Splitter pattern using an xpath expression to split the incoming xml.

{snippet:id=xpath-splitter|lang=xml|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-eip/src/test/resources/org/apache/servicemix/eip/spring.xml}