Modified: websites/production/camel/content/pipes-and-filters.html
==============================================================================
--- websites/production/camel/content/pipes-and-filters.html (original)
+++ websites/production/camel/content/pipes-and-filters.html Fri Aug 25
09:20:43 2017
@@ -36,17 +36,6 @@
<![endif]-->
- <link href='//camel.apache.org/styles/highlighter/styles/shCoreCamel.css'
rel='stylesheet' type='text/css' />
- <link href='//camel.apache.org/styles/highlighter/styles/shThemeCamel.css'
rel='stylesheet' type='text/css' />
- <script src='//camel.apache.org/styles/highlighter/scripts/shCore.js'
type='text/javascript'></script>
- <script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js'
type='text/javascript'></script>
- <script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js'
type='text/javascript'></script>
- <script src='//camel.apache.org/styles/highlighter/scripts/shBrushPlain.js'
type='text/javascript'></script>
-
- <script type="text/javascript">
- SyntaxHighlighter.defaults['toolbar'] = false;
- SyntaxHighlighter.all();
- </script>
<title>
Apache Camel: Pipes and Filters
@@ -86,47 +75,35 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3
id="PipesandFilters-PipesandFilters">Pipes and Filters</h3><p>Camel supports
the <a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html";
rel="nofollow">Pipes and Filters</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a> in various
ways.</p><p><span class="confluence-embedded-file-wrapper"><img
class="confluence-embedded-image confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/PipesAndFilters.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/PipesAndFilters.gif";></span></p><p>With
Camel you can split your processing across multiple independent <a
shape="rect" href="endpoint.html">Endpoint</a> instances which can then be
chained together.</p><h4 id="PipesandFilters-UsingRoutingLogic">Using Routing
Logic</h4><p>You can create pipelines of logic using multiple <a shape="rect"
href="endpoint.html">End
point</a> or <a shape="rect" href="message-translator.html">Message
Translator</a> instances as follows</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
-from("direct:a").pipeline("direct:x",
"direct:y", "direct:z", "mock:result");
-]]></script>
-</div></div>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).<p>In Spring
XML you can use the <strong><code><pipeline/></code></strong>
element</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
- <from uri="activemq:SomeQueue"/>
+<div class="wiki-content maincontent"><h3
id="PipesandFilters-PipesandFilters">Pipes and Filters</h3><p>Camel supports
the <a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html";
rel="nofollow">Pipes and Filters</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a> in various
ways.</p><p><span class="confluence-embedded-file-wrapper"><img
class="confluence-embedded-image confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/PipesAndFilters.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/PipesAndFilters.gif";></span></p><p>With
Camel you can split your processing across multiple independent <a
shape="rect" href="endpoint.html">Endpoint</a> instances which can then be
chained together.</p><h4 id="PipesandFilters-UsingRoutingLogic">Using Routing
Logic</h4><p>You can create pipelines of logic using multiple <a shape="rect"
href="endpoint.html">End
point</a> or <a shape="rect" href="message-translator.html">Message
Translator</a> instances as
follows<plain-text-body>{snippet:id=example|lang=java|url=camel/trunk/camel-core/src/test/java/org/apache/camel/processor/PipelineTest.java}</plain-text-body>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).</p><p>In Spring XML you can use
the <strong><code><pipeline/></code></strong> element</p><parameter
ac:name="language">xml</parameter><plain-text-body><route>
+ <from uri="activemq:SomeQueue"/>
<pipeline>
- <bean ref="foo"/>
- <bean ref="bar"/>
- <to uri="activemq:OutputQueue"/>
+ <bean ref="foo"/>
+ <bean ref="bar"/>
+ <to uri="activemq:OutputQueue"/>
</pipeline>
</route>
-]]></script>
-</div></div><p>In the above the pipeline element is actually unnecessary, you
could use this:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
- <from uri="activemq:SomeQueue"/>
- <bean ref="foo"/>
- <bean ref="bar"/>
- <to uri="activemq:OutputQueue"/>
+</plain-text-body><p>In the above the pipeline element is actually
unnecessary, you could use this:</p><parameter
ac:name="language">xml</parameter><plain-text-body><route>
+ <from uri="activemq:SomeQueue"/>
+ <bean ref="foo"/>
+ <bean ref="bar"/>
+ <to uri="activemq:OutputQueue"/>
</route>
-]]></script>
-</div></div><p>which is a bit more explicit.</p><p>However if you wish to
use <strong><code><multicast/></code></strong> to avoid a pipeline -
to send the same message into multiple pipelines - then
the <strong><code><pipeline/></code></strong> element comes into its
own:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
- <from uri="activemq:SomeQueue"/>
+</plain-text-body><p>which is a bit more explicit.</p><p>However if you wish
to use <strong><code><multicast/></code></strong> to avoid a
pipeline - to send the same message into multiple pipelines - then
the <strong><code><pipeline/></code></strong> element comes into its
own:</p><parameter
ac:name="language">xml</parameter><plain-text-body><route>
+ <from uri="activemq:SomeQueue"/>
<multicast>
<pipeline>
- <bean ref="something"/>
- <to uri="log:Something"/>
+ <bean ref="something"/>
+ <to uri="log:Something"/>
</pipeline>
<pipeline>
- <bean ref="foo"/>
- <bean ref="bar"/>
- <to uri="activemq:OutputQueue"/>
+ <bean ref="foo"/>
+ <bean ref="bar"/>
+ <to uri="activemq:OutputQueue"/>
</pipeline>
</multicast>
</route>
-]]></script>
-</div></div><p>In the above example we are routing from a single <a
shape="rect" href="endpoint.html">Endpoint</a> to a list of different endpoints
specified using <a shape="rect" href="uris.html">URIs</a>. If you find the
above a bit confusing, try reading about the <a shape="rect"
href="architecture.html">Architecture</a> or try the <a shape="rect"
href="examples.html">Examples</a></p><p></p><h4
id="PipesandFilters-UsingThisPattern">Using This Pattern</h4>
-
-<p>If you would like to use this EIP Pattern then please read the <a
shape="rect" href="getting-started.html">Getting Started</a>, you may also find
the <a shape="rect" href="architecture.html">Architecture</a> useful
particularly the description of <a shape="rect"
href="endpoint.html">Endpoint</a> and <a shape="rect"
href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect"
href="examples.html">Examples</a> first before trying this pattern
out.</p></div>
+</plain-text-body><p>In the above example we are routing from a single <a
shape="rect" href="endpoint.html">Endpoint</a> to a list of different endpoints
specified using <a shape="rect" href="uris.html">URIs</a>. If you find the
above a bit confusing, try reading about the <a shape="rect"
href="architecture.html">Architecture</a> or try the <a shape="rect"
href="examples.html">Examples</a></p><p><parameter ac:name=""><a shape="rect"
href="using-this-pattern.html">Using This Pattern</a></parameter></p></div>
</td>
<td valign="top">
<div class="navigation">
![http://www.enterpriseintegrationpatterns.com/img/PipesAndFilters.gif"](http://www.enterpriseintegrationpatterns.com/img/PipesAndFilters.gif"){kind=link}
