Red Hat Training

A Red Hat training course is available for Red Hat Fuse

A.7. Pipeline


The ServiceMix EIP pipeline pattern, shown in Figure A.4, “Pipes and Filters Pattern”, is used to pass messages through a single transformer endpoint, where the transformer's input is taken from the source endpoint and the transformer's output is routed to the target endpoint. This pattern is thus a special case of the more general Apache Camel pipes and filters pattern, which enables you to pass an In message through multiple transformer endpoints.

Figure A.4. Pipes and Filters Pattern

Pipes and filters pattern

Example ServiceMix EIP route

Example A.10, “ServiceMix EIP Pipeline” shows how to define a pipeline using the ServiceMix EIP component. Incoming messages are passed into the transformer endpoint, test:decrypt, and the output from the transformer endpoint is then passed into the target endpoint, test:plaintextOrder.

Example A.10. ServiceMix EIP Pipeline

<eip:pipeline service="test:pipeline" endpoint="endpoint">
    <eip:exchange-target service="test:decrypt" />
    <eip:exchange-target service="test:plaintextOrder" />

Equivalent Apache Camel XML route

Example A.11, “Apache Camel Pipeline Using XML” shows how to define an equivalent route using Apache Camel XML configuration.

Example A.11. Apache Camel Pipeline Using XML

  <from uri="jbi:endpoint:"/>
  <to uri="jbi:service:"/>
  <to uri="jbi:service:"/>

Equivalent Apache Camel Java DSL route

Example A.12, “Apache Camel Pipeline Using Java DSL” shows how to define an equivalent route using the Apache Camel Java DSL.

Example A.12. Apache Camel Pipeline Using Java DSL

    pipeline("jbi:service:", "jbi:service:");