camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r890987 - in /websites/production/camel/content: cache/main.pageCache wire-tap.html
Date Thu, 19 Dec 2013 00:23:33 GMT
Author: buildbot
Date: Thu Dec 19 00:23:33 2013
New Revision: 890987

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/wire-tap.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/wire-tap.html
==============================================================================
--- websites/production/camel/content/wire-tap.html (original)
+++ websites/production/camel/content/wire-tap.html Thu Dec 19 00:23:33 2013
@@ -75,54 +75,23 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3 id="WireTap-WireTap">Wire Tap</h3>
-
-<p><a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/WireTap.html"
rel="nofollow">Wire Tap</a> (from the <a shape="rect" href="enterprise-integration-patterns.html">EIP
patterns</a>) allows you to route messages to a separate location while they are being
forwarded to the ultimate destination.</p>
-
-<p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif"
data-image-src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif"></p>
-
-    <div class="aui-message hint shadowed information-macro">
+<div class="wiki-content maincontent"><h3 id="WireTap-WireTap">Wire Tap</h3><p><a
shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/WireTap.html"
rel="nofollow">Wire Tap</a> (from the <a shape="rect" href="enterprise-integration-patterns.html">EIP
patterns</a>) allows you to route messages to a separate location while they are being
forwarded to the ultimate destination.</p><p><img class="confluence-embedded-image
confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif"
data-image-src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif"></p>
   <div class="aui-message hint shadowed information-macro">
                     <p class="title">Streams</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">
-                            
-<p>If you <a shape="rect" href="wire-tap.html">Wire Tap</a> a stream message
body then you should consider enabling <a shape="rect" href="stream-caching.html">Stream
Caching</a> to ensure the message body can be read at each endpoint. See more details
at <a shape="rect" href="stream-caching.html">Stream Caching</a>.  </p>
+                            <p>If you <a shape="rect" href="wire-tap.html">Wire
Tap</a> a stream message body then you should consider enabling <a shape="rect" href="stream-caching.html">Stream
caching</a> to ensure the message body can be read at each endpoint. See more details
at <a shape="rect" href="stream-caching.html">Stream caching</a>.</p>
                     </div>
     </div>
-
-
-<h3 id="WireTap-Options">Options</h3>
-
-<div class="confluenceTableSmall">
+<h3 id="WireTap-Options">Options</h3><div class="confluenceTableSmall">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>uri</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> The URI of the endpoint to which
the wire-tapped message will be sent. You should use either <code>uri</code> or
<code>ref</code>. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>ref</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Reference identifier of the endpoint
to which the wire-tapped message will be sent. You should use either <code>uri</code>
or <code>ref</code>. </p></td></tr><tr><td colspan="1"
rows
 pan="1" class="confluenceTd"><p> <code>executorServiceRef</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Reference identifier of a custom
<a shape="rect" href="threading-model.html" title="Threading Model">Thread Pool</a>
to use when processing the wire-tapped messages. If not set, Camel will use a default thread
pool. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>processorRef</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Reference identifier of a custom <a shape="rect" href="processor.html"
title="Processor">Processor</a> to use for creating a new message (e.g., the "send
a new message" mode). See below. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>copy</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p><
 /td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.3</strong>: Whether to copy the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>
before wire-tapping the message. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>onPrepareRef</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong>
Reference identifier of a custom <a shape="rect" href="processor.html" title="Processor">Processor</a>
to prepare the copy of the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>
to be wire-tapped. This allows you to do any custom logic, such as deep-cloning the message
payload. </p></td></tr></tbody></table>
-</div>
-
-
-<h3 id="WireTap-WireTapthreadpool">WireTap thread pool</h3>
-
-<p>The <a shape="rect" href="wire-tap.html">Wire Tap</a> uses a thread
pool to process the tapped messages. This thread pool will by default use the settings detailed
at <a shape="rect" href="threading-model.html">Threading Model</a>.  In particular,
when the pool is exhausted (with all threads utilized), further wiretaps will be executed
synchronously by the calling thread.  To remedy this, you can configure an explicit thread
pool on the <a shape="rect" href="wire-tap.html">Wire Tap</a> having either a
different rejection policy, a larger worker queue, or more worker threads.</p>
-
-<h3 id="WireTap-WireTapnode">WireTap node</h3>
-
-<p>Camel's Wire Tap node supports two flavors when tapping an <a shape="rect" href="exchange.html">Exchange</a>:</p>
-
-<p>-With the traditional Wire Tap, Camel will copy the original <a shape="rect"
href="exchange.html">Exchange</a> and set its <a shape="rect" href="exchange-pattern.html">Exchange
Pattern</a> to <strong>InOnly</strong>, as we want the tapped <a shape="rect"
href="exchange.html">Exchange</a> to be sent in a <em>fire and forget</em>
style. The tapped <a shape="rect" href="exchange.html">Exchange</a> is then sent
in a separate thread so it can run in parallel with the original.</p>
-
-<p>-Camel also provides an option of sending a new <a shape="rect" href="exchange.html">Exchange</a>
allowing you to populate it with new values.</p>
-
-<h4 id="WireTap-Sendingacopy(traditionalwiretap)">Sending a copy (traditional wiretap)</h4>
-<p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent
Builders</a></strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+</div><h3 id="WireTap-WireTapthreadpool">WireTap thread pool</h3><p>The
<a shape="rect" href="wire-tap.html">Wire Tap</a> uses a thread pool to process
the tapped messages. This thread pool will by default use the settings detailed at <a shape="rect"
href="threading-model.html">Threading Model</a>. In particular, when the pool is
exhausted (with all threads utilized), further wiretaps will be executed synchronously by
the calling thread. To remedy this, you can configure an explicit thread pool on the <a
shape="rect" href="wire-tap.html">Wire Tap</a> having either a different rejection
policy, a larger worker queue, or more worker threads.</p><h3 id="WireTap-WireTapnode">WireTap
node</h3><p>Camel's Wire Tap node supports two flavors when tapping an <a shape="rect"
href="exchange.html">Exchange</a>:</p><p>-With the traditional Wire Tap,
Camel will copy the original <a shape="rect" href="exchange.html">Exchange</a>
and set its <a shape="rect" href="exchange-pattern.html">Exchange Patt
 ern</a> to <strong>InOnly</strong>, as we want the tapped <a shape="rect"
href="exchange.html">Exchange</a> to be sent in a <em>fire and forget</em>
style. The tapped <a shape="rect" href="exchange.html">Exchange</a> is then sent
in a separate thread so it can run in parallel with the original.</p><p>-Camel
also provides an option of sending a new <a shape="rect" href="exchange.html">Exchange</a>
allowing you to populate it with new values.</p><h4 id="WireTap-Sendingacopy(traditionalwiretap)">Sending
a copy (traditional wiretap)</h4><p><strong>Using the <a shape="rect"
href="fluent-builders.html">Fluent Builders</a></strong></p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     .to(&quot;log:foo&quot;)
     .wireTap(&quot;direct:tap&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring
XML Extensions</a></strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+</div></div><p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring
XML Extensions</a></strong></p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -131,16 +100,7 @@ from(&quot;direct:start&quot;)
     &lt;to uri=&quot;mock:result&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<h4 id="WireTap-Sendinganew">Sending a new <a shape="rect" href="exchange.html">Exchange</a></h4>
-<p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent
Builders</a></strong><br clear="none">
-Camel supports either a processor or an <a shape="rect" href="expression.html">Expression</a>
to populate the new <a shape="rect" href="exchange.html">Exchange</a>. Using a
processor gives you full power over how the <a shape="rect" href="exchange.html">Exchange</a>
is populated as you can set properties, headers, et cetera. An <a shape="rect" href="expression.html">Expression</a>
can only be used to set the IN body. </p>
-
-<p>From <strong>Camel 2.3</strong> onwards the <a shape="rect" href="expression.html">Expression</a>
or <a shape="rect" href="processor.html">Processor</a> is pre-populated with a
copy of the original <a shape="rect" href="exchange.html">Exchange</a>, which
allows you to access the original message when you prepare a new <a shape="rect" href="exchange.html">Exchange</a>
to be sent. You can use the <code>copy</code> option (enabled by default) to indicate
whether you want this.  If you set <code>copy=false</code>, then it works as in
Camel 2.2 or older where the <a shape="rect" href="exchange.html">Exchange</a>
will be empty.</p>
-
-<p>Below is the processor variation. This example is from Camel 2.3, where we disable
<code>copy</code> by passing in <code>false</code> to create a new,
empty <a shape="rect" href="exchange.html">Exchange</a>. </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+</div></div><h4 id="WireTap-Sendinganew">Sending a new <a shape="rect"
href="exchange.html">Exchange</a></h4><p><strong>Using the <a
shape="rect" href="fluent-builders.html">Fluent Builders</a></strong><br
clear="none"> Camel supports either a processor or an <a shape="rect" href="expression.html">Expression</a>
to populate the new <a shape="rect" href="exchange.html">Exchange</a>. Using a
processor gives you full power over how the <a shape="rect" href="exchange.html">Exchange</a>
is populated as you can set properties, headers, et cetera. An <a shape="rect" href="expression.html">Expression</a>
can only be used to set the IN body.</p><p>From <strong>Camel 2.3</strong>
onwards the <a shape="rect" href="expression.html">Expression</a> or <a shape="rect"
href="processor.html">Processor</a> is pre-populated with a copy of the original
<a shape="rect" href="exchange.html">Exchange</a>, which allows you to access
the original message when you prepare a new <a shape="rect" href="exchange
 .html">Exchange</a> to be sent. You can use the <code>copy</code> option
(enabled by default) to indicate whether you want this. If you set <code>copy=false</code>,
then it works as in Camel 2.2 or older where the <a shape="rect" href="exchange.html">Exchange</a>
will be empty.</p><p>Below is the processor variation. This example is from Camel
2.3, where we disable <code>copy</code> by passing in <code>false</code>
to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     .wireTap(&quot;direct:foo&quot;, false, new Processor() {
@@ -153,10 +113,7 @@ from(&quot;direct:start&quot;)
 
 from(&quot;direct:foo&quot;).to(&quot;mock:foo&quot;);
 ]]></script>
-</div></div>
-
-<p>Here is the <a shape="rect" href="expression.html">Expression</a> variation.
This example is from Camel 2.3, where we disable <code>copy</code> by passing
in <code>false</code> to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>.
</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+</div></div><p>Here is the <a shape="rect" href="expression.html">Expression</a>
variation. This example is from Camel 2.3, where we disable <code>copy</code>
by passing in <code>false</code> to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     .wireTap(&quot;direct:foo&quot;, false, constant(&quot;Bye World&quot;))
@@ -164,11 +121,7 @@ from(&quot;direct:start&quot;)
 
 from(&quot;direct:foo&quot;).to(&quot;mock:foo&quot;);
 ]]></script>
-</div></div>
-
-<p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring
XML Extensions</a></strong><br clear="none">
-The processor variation, which uses a <strong>processorRef</strong> attribute
to refer to a Spring bean by ID: </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+</div></div><p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring
XML Extensions</a></strong><br clear="none"> The processor variation, which
uses a <strong>processorRef</strong> attribute to refer to a Spring bean by ID:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start2&quot;/&gt;
@@ -176,10 +129,7 @@ The processor variation, which uses a <s
     &lt;to uri=&quot;mock:result&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<p>Here is the <a shape="rect" href="expression.html">Expression</a> variation,
where the expression is defined in the <strong>body</strong> tag: </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+</div></div><p>Here is the <a shape="rect" href="expression.html">Expression</a>
variation, where the expression is defined in the <strong>body</strong> tag:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -189,10 +139,7 @@ The processor variation, which uses a <s
     &lt;to uri=&quot;mock:result&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<p>This variation accesses the body of the original message and creates a new <a
shape="rect" href="exchange.html">Exchange</a> based on the <a shape="rect" href="expression.html">Expression</a>.
 It will create a new Exchange and have the body contain <code>"Bye ORIGINAL BODY MESSAGE
HERE"</code></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+</div></div><p>This variation accesses the body of the original message
and creates a new <a shape="rect" href="exchange.html">Exchange</a> based on the
<a shape="rect" href="expression.html">Expression</a>. It will create a new Exchange
and have the body contain <code>"Bye ORIGINAL BODY MESSAGE HERE"</code></p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -202,23 +149,7 @@ The processor variation, which uses a <s
     &lt;to uri=&quot;mock:result&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<h4 id="WireTap-FurtherExample">Further Example</h4>
-
-<p>For another example of this pattern, refer to the <a shape="rect" class="external-link"
href="http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/WireTapTest.java">wire
tap test case</a>.</p>
-
-<h3 id="WireTap-SendinganewandsetheadersinDSL">Sending a new <a shape="rect" href="exchange.html">Exchange</a>
and set headers in DSL</h3>
-<p><strong>Available as of Camel 2.8</strong></p>
-
-<p>If you send a new message using <a shape="rect" href="wire-tap.html">Wire
Tap</a>, then you could only set the message body using an <a shape="rect" href="expression.html">Expression</a>
from the DSL. If you also need to set headers, you would have to use a <a shape="rect"
href="processor.html">Processor</a>. In Camel 2.8 onwards, you can now set headers
as well in the DSL.</p>
-
-<p>The following example sends a new message which has</p>
-<ul class="alternate"><li>"Bye World" as message body</li><li>a header
with key "id" with the value 123</li><li>a header with key "date" which has current
date as value</li></ul>
-
-
-<h4 id="WireTap-JavaDSL">Java DSL</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+</div></div><h4 id="WireTap-FurtherExample">Further Example</h4><p>For
another example of this pattern, refer to the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/WireTapTest.java">wire
tap test case</a>.</p><h3 id="WireTap-SendinganewandsetheadersinDSL">Sending
a new <a shape="rect" href="exchange.html">Exchange</a> and set headers in DSL</h3><p><strong>Available
as of Camel 2.8</strong></p><p>If you send a new message using <a shape="rect"
href="wire-tap.html">Wire Tap</a>, then you could only set the message body using
an <a shape="rect" href="expression.html">Expression</a> from the DSL. If you
also need to set headers, you would have to use a <a shape="rect" href="processor.html">Processor</a>.
In Camel 2.8 onwards, you can now set headers as well in the DSL.</p><p>The following
example sends a new message which has</p><ul class="alternate"><li>"Bye
World" as message body</li><li>a hea
 der with key "id" with the value 123</li><li>a header with key "date" which has
current date as value</li></ul><h4 id="WireTap-JavaDSL">Java DSL</h4><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // tap a new message and send it to direct:tap
@@ -236,11 +167,7 @@ from(&quot;direct:start&quot;)
 from(&quot;direct:tap&quot;)
     .to(&quot;mock:tap&quot;);
 ]]></script>
-</div></div>
-
-<h4 id="WireTap-XMLDSL">XML DSL</h4>
-<p>The XML DSL is slightly different than Java DSL in how you configure the message
body and headers using &lt;body&gt; and &lt;setHeader&gt;:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+</div></div><h4 id="WireTap-XMLDSL">XML DSL</h4><p>The XML
DSL is slightly different than Java DSL in how you configure the message body and headers
using &lt;body&gt; and &lt;setHeader&gt;:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -256,16 +183,7 @@ from(&quot;direct:tap&quot;)
     &lt;to uri=&quot;mock:result&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-
-<h3 id="WireTap-UsingonPreparetoexecutecustomlogicwhenpreparingmessages">Using onPrepare
to execute custom logic when preparing messages</h3>
-<p><strong>Available as of Camel 2.8</strong></p>
-
-<p>See details at <a shape="rect" href="multicast.html">Multicast</a></p>
-
-
-<h4 id="WireTap-UsingThisPattern">Using This Pattern</h4>
+</div></div><h3 id="WireTap-UsingonPreparetoexecutecustomlogicwhenpreparingmessages">Using
onPrepare to execute custom logic when preparing messages</h3><p><strong>Available
as of Camel 2.8</strong></p><p>See details at <a shape="rect" href="multicast.html">Multicast</a></p><p></p><h4
id="WireTap-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>
         </td>



Mime
View raw message