[CONF] Apache Camel > Pipes and Filters

[confluence]

Pipes and Filters Page edited by Christian Mueller Comment: Removed the deprecated Camel 1.x documentations Changes (1) ... Though pipeline is the default mode of operation when you specify multiple outputs in Camel. The opposite to pipeline is multicast; which fires the same message into each of its outputs. (See the example below). In Spring XML you can use the <pipeline/> element as of 1.4.0 onwards {code} ... Full Content Pipes and Filters Camel supports the Pipes and Filters from the EIP patterns in various ways. With Camel you can split your processing across multiple independent Endpoint instances which can then be chained together. Using Routing Logic You can create pipelines of logic using multiple Endpoint or Message Translator instances as follows from("direct:a").pipeline("direct:x", "direct:y", "direct:z", "mock:result"); Though pipeline is the default mode of operation when you specify multiple outputs in Camel. The opposite to pipeline is multicast; which fires the same message into each of its outputs. (See the example below). In Spring XML you can use the <pipeline/> element <route> <from uri="activemq:SomeQueue"/> <pipeline> <bean ref="foo"/> <bean ref="bar"/> <to uri="activemq:OutputQueue"/> </pipeline> </route> In the above the pipeline element is actually unnecessary, you could use this... <route> <from uri="activemq:SomeQueue"/> <bean ref="foo"/> <bean ref="bar"/> <to uri="activemq:OutputQueue"/> </route> Its just a bit more explicit. However if you wish to use <multicast/> to avoid a pipeline - to send the same message into multiple pipelines - then the <pipeline/> element comes into its own. <route> <from uri="activemq:SomeQueue"/> <multicast> <pipeline> <bean ref="something"/> <to uri="log:Something"/> </pipeline> <pipeline> <bean ref="foo"/> <bean ref="bar"/> <to uri="activemq:OutputQueue"/> </pipeline> </multicast> </route> In the above example we are routing from a single Endpoint to a list of different endpoints specified using URIs. If you find the above a bit confusing, try reading about the Architecture or try the Examples Using This Pattern If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out. Change Notification Preferences View Online | View Changes | Add Comment