camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r910692 - in /websites/production/camel/content: cache/main.pageCache wire-tap.html
Date Sat, 31 May 2014 13:18:48 GMT
Author: buildbot
Date: Sat May 31 13:18:48 2014
New Revision: 910692

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 Sat May 31 13:18:48 2014
@@ -93,7 +93,7 @@
                             <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="table-wrap"><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>re
 f</code>.</p></td></tr><tr><td colspan="1" rowspan="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">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">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">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">Processor</a>
to prepare the copy of the <a shape="rect" href="exchange.html">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.ht
 ml">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 paralle
 l with the original. Beware that only the Exchange is copied - Wire Tap won't do a deep clone.
So all copies could share objects from the original Exchange.</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">
+<h3 id="WireTap-Options">Options</h3><div class="table-wrap"><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>re
 f</code>.</p></td></tr><tr><td colspan="1" rowspan="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">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">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">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">Processor</a>
to prepare the copy of the <a shape="rect" href="exchange.html">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.ht
 ml">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 InOnly, as we want the tapped <a shape="rect" href="exchange.html">Exchange</a>
to be sent in a fire and forget 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. Bewar
 e that only the Exchange is copied - Wire Tap won't do a deep clone (unless you specify a
custom processor via <em>onPrepareRef</em> which does that). So all copies could
share objects from the original Exchange.</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;)



Mime
View raw message