camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1017266 [8/17] - in /websites/production/camel/content: ./ cache/
Date Fri, 25 Aug 2017 09:20:43 GMT
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(&quot;direct:a&quot;).pipeline(&quot;direct:x&quot;, &quot;direct:y&quot;,
&quot;direct:z&quot;, &quot;mock:result&quot;);
-]]></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&#160;<strong><code>&lt;pipeline/&gt;</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[&lt;route&gt;
-  &lt;from uri=&quot;activemq:SomeQueue&quot;/&gt;
+<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&#160;<strong><code>&lt;pipeline/&gt;</code></strong>
element</p><parameter ac:name="language">xml</parameter><plain-text-body>&lt;route&gt;
+  &lt;from uri="activemq:SomeQueue"/&gt;
   &lt;pipeline&gt;
-    &lt;bean ref=&quot;foo&quot;/&gt;
-    &lt;bean ref=&quot;bar&quot;/&gt;
-    &lt;to uri=&quot;activemq:OutputQueue&quot;/&gt;
+    &lt;bean ref="foo"/&gt;
+    &lt;bean ref="bar"/&gt;
+    &lt;to uri="activemq:OutputQueue"/&gt;
   &lt;/pipeline&gt;
 &lt;/route&gt;
-]]></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[&lt;route&gt;
-  &lt;from uri=&quot;activemq:SomeQueue&quot;/&gt;
-  &lt;bean ref=&quot;foo&quot;/&gt;
-  &lt;bean ref=&quot;bar&quot;/&gt;
-  &lt;to uri=&quot;activemq:OutputQueue&quot;/&gt;
+</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>&lt;route&gt;
+  &lt;from uri="activemq:SomeQueue"/&gt;
+  &lt;bean ref="foo"/&gt;
+  &lt;bean ref="bar"/&gt;
+  &lt;to uri="activemq:OutputQueue"/&gt;
 &lt;/route&gt;
-]]></script>
-</div></div><p>which is a bit more explicit.</p><p>However
if you wish to use&#160;<strong><code>&lt;multicast/&gt;</code></strong>
to avoid a pipeline - to send the same message into multiple pipelines - then the&#160;<strong><code>&lt;pipeline/&gt;</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[&lt;route&gt;
-  &lt;from uri=&quot;activemq:SomeQueue&quot;/&gt;
+</plain-text-body><p>which is a bit more explicit.</p><p>However
if you wish to use&#160;<strong><code>&lt;multicast/&gt;</code></strong>
to avoid a pipeline - to send the same message into multiple pipelines - then the&#160;<strong><code>&lt;pipeline/&gt;</code></strong>
element comes into its own:</p><parameter ac:name="language">xml</parameter><plain-text-body>&lt;route&gt;
+  &lt;from uri="activemq:SomeQueue"/&gt;
   &lt;multicast&gt;
     &lt;pipeline&gt;
-      &lt;bean ref=&quot;something&quot;/&gt;
-      &lt;to uri=&quot;log:Something&quot;/&gt;
+      &lt;bean ref="something"/&gt;
+      &lt;to uri="log:Something"/&gt;
     &lt;/pipeline&gt;
     &lt;pipeline&gt;
-      &lt;bean ref=&quot;foo&quot;/&gt;
-      &lt;bean ref=&quot;bar&quot;/&gt;
-      &lt;to uri=&quot;activemq:OutputQueue&quot;/&gt;
+      &lt;bean ref="foo"/&gt;
+      &lt;bean ref="bar"/&gt;
+      &lt;to uri="activemq:OutputQueue"/&gt;
     &lt;/pipeline&gt;
   &lt;/multicast&gt;
 &lt;/route&gt;
-]]></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">



Mime
View raw message