Author: buildbot
Date: Fri Dec 20 05:37:26 2013
New Revision: 891144
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/content-based-router.html
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/content-based-router.html
==============================================================================
--- websites/production/camel/content/content-based-router.html (original)
+++ websites/production/camel/content/content-based-router.html Fri Dec 20
05:37:26 2013
@@ -41,7 +41,6 @@
<script src='http://camel.apache.org/styles/highlighter/scripts/shCore.js'
type='text/javascript'></script>
<script
src='http://camel.apache.org/styles/highlighter/scripts/shBrushJava.js'
type='text/javascript'></script>
<script
src='http://camel.apache.org/styles/highlighter/scripts/shBrushXml.js'
type='text/javascript'></script>
- <script
src='http://camel.apache.org/styles/highlighter/scripts/shBrushPlain.js'
type='text/javascript'></script>
<script type="text/javascript">
SyntaxHighlighter.defaults['toolbar'] = false;
@@ -86,21 +85,11 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3
id="ContentBasedRouter-ContentBasedRouter">Content Based Router</h3>
-
-<p>The <a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/ContentBasedRouter.html"
rel="nofollow">Content Based Router</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a> allows you to
route messages to the correct destination based on the contents of the message
exchanges.</p>
-
-<p><img class="confluence-embedded-image confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/ContentBasedRouter.gif"
data-image-src="http://www.enterpriseintegrationpatterns.com/img/ContentBasedRouter.gif"></p>
-
-<p>The following example shows how to route a request from an input
<strong>seda:a</strong> endpoint to either <strong>seda:b</strong>,
<strong>seda:c</strong> or <strong>seda:d</strong> depending on the evaluation
of various <a shape="rect" href="predicate.html">Predicate</a> expressions</p>
-
-<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[
-RouteBuilder builder = new RouteBuilder() {
+<div class="wiki-content maincontent"><h3
id="ContentBasedRouter-ContentBasedRouter">Content Based Router</h3><p>The <a
shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/ContentBasedRouter.html"
rel="nofollow">Content Based Router</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a> allows you to
route messages to the correct destination based on the contents of the message
exchanges.</p><p><img class="confluence-embedded-image
confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/ContentBasedRouter.gif"
data-image-src="http://www.enterpriseintegrationpatterns.com/img/ContentBasedRouter.gif"></p><p>The
following example shows how to route a request from an input
<strong>seda:a</strong> endpoint to either <strong>seda:b</strong>,
<strong>seda:c</strong> or <strong>seda:d</strong> depending on the evaluation
of various <a shape="rect" href="predicate.html">Predicate</a> expressions</
p><p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent
Builders</a></strong></p><p> </p><p><strong><br
clear="none"></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[RouteBuilder builder = new RouteBuilder() {
public void configure() {
errorHandler(deadLetterChannel("mock:error"));
-
+
from("direct:a")
.choice()
.when(header("foo").isEqualTo("bar"))
@@ -110,23 +99,15 @@ RouteBuilder builder = new RouteBuilder(
.otherwise()
.to("direct:d");
}
-};
-]]></script>
-</div></div>
-
- <div class="aui-message success shadowed information-macro">
+};]]></script>
+</div></div> <div class="aui-message success shadowed information-macro">
<span class="aui-icon icon-success">Icon</span>
<div class="message-content">
-
-<p>See <a shape="rect"
href="why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.html">Why can I
not use when or otherwise in a Java Camel route</a> if you have problems with
the Java DSL, accepting using <code>when</code> or <code>otherwise</code>.</p>
+ <p>See <a shape="rect"
href="why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.html">Why can I
not use when or otherwise in a Java Camel route</a> if you have problems with
the Java DSL, accepting using <code>when</code> or <code>otherwise</code>.</p>
</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[
-<camelContext errorHandlerRef="errorHandler"
xmlns="http://camel.apache.org/schema/spring">
+<p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring
XML Extensions</a></strong></p><div class="line number1 index0
alt2"><p> </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[<camelContext
errorHandlerRef="errorHandler"
xmlns="http://camel.apache.org/schema/spring">
<route>
<from uri="direct:a"/>
<choice>
@@ -143,12 +124,8 @@ RouteBuilder builder = new RouteBuilder(
</otherwise>
</choice>
</route>
-</camelContext>
-]]></script>
-</div></div>
-
-<p>For further examples of this pattern in use you could look at the <a
shape="rect" class="external-link"
href="http://svn.apache.org/viewvc/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/ChoiceTest.java?view=markup">junit
test case</a></p>
-<h4 id="ContentBasedRouter-UsingThisPattern">Using This Pattern</h4>
+</camelContext>]]></script>
+</div></div><p><span style="line-height: 1.4285715;">For further examples of
this pattern in use you could look at the </span><a shape="rect"
class="external-link"
href="http://svn.apache.org/viewvc/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/ChoiceTest.java?view=markup"
style="line-height: 1.4285715;">junit test case</a></p></div><p></p><h4
id="ContentBasedRouter-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>
Modified: websites/production/camel/content/wire-tap.html
==============================================================================
--- websites/production/camel/content/wire-tap.html (original)
+++ websites/production/camel/content/wire-tap.html Fri Dec 20 05:37:26 2013
@@ -93,9 +93,8 @@
<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">
-<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> </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> </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> </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> </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> </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 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">
+<h3 id="WireTap-Options">Options</h3><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> </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> </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" rowspan="1" class="confluenceTd"><p>
<code>executorServiceRef</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </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> </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="conf
luenceTd"><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> </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>
+<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">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from("direct:start")
.to("log:foo")