You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2014/06/15 12:21:13 UTC
svn commit: r912628 [2/3] - in /websites/production/camel/content: ./ cache/
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Sun Jun 15 10:21:12 2014
@@ -4139,11 +4139,11 @@ While not actual tutorials you might fin
</div>
</div>
<h2 id="BookInOnePage-Preface">Preface</h2><p>This tutorial aims to guide the reader through the stages of creating a project which uses Camel to facilitate the routing of messages from a JMS queue to a <a shape="rect" class="external-link" href="http://www.springramework.org" rel="nofollow">Spring</a> service. The route works in a synchronous fashion returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1402629507711 {padding: 0px;}
-div.rbtoc1402629507711 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1402629507711 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1402827458826 {padding: 0px;}
+div.rbtoc1402827458826 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1402827458826 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1402629507711">
+/*]]>*/</style></p><div class="toc-macro rbtoc1402827458826">
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Preface">Preface</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-About">About</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-CreatetheCamelProject">Create the Camel Project</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-UpdatethePOMwithDependencies">Update the POM with Dependencies</a></li></ul>
</li><li><a shape="rect" href="#Tutorial-JmsRemoting-WritingtheServer">Writing the Server</a>
@@ -6329,11 +6329,11 @@ So we completed the last piece in the pi
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1402629508260 {padding: 0px;}
-div.rbtoc1402629508260 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1402629508260 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1402827459079 {padding: 0px;}
+div.rbtoc1402827459079 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1402827459079 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1402629508260">
+/*]]>*/</style><div class="toc-macro rbtoc1402827459079">
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis 1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Introduction">Introduction</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-SettinguptheprojecttorunAxis">Setting up the project to run Axis</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Maven2">Maven 2</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-wsdl">wsdl</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-ConfiguringAxis">Configuring Axis</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-RunningtheExample">Running the Example</a></li></ul>
@@ -16217,41 +16217,16 @@ from("direct:c").routingSlip(h
</div></div><h4 id="BookInOnePage-FurtherExamples.1">Further Examples</h4><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/routingslip">routing slip test cases</a>.</p><p></p><h4 id="BookInOnePage-UsingThisPattern.23">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>
-<h3 id="BookInOnePage-Throttler">Throttler</h3>
-
-<p>The Throttler Pattern allows you to ensure that a specific endpoint does not get overloaded, or that we don't exceed an agreed SLA with some external service.</p>
-
-<h3 id="BookInOnePage-Options.14">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>maximumRequestsPerPeriod</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Maximum number of requests per period to throttle. This option must be provided as a positive number. Notice, in the XML DSL, from <strong>Camel 2.8</strong> onwards this option is configured using an <a shape="rect" href="expression.html" title="Expression">Expression</a> instead of an attribute. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>timePeriodMillis</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>1000</code> </p></td><td colspan="1" rows
pan="1" class="confluenceTd"><p> The time period in milliseconds, in which the throttler will allow at most <code>maximumRequestsPerPeriod</code> number of messages. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>asyncDelayed</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.4:</strong> If enabled then any messages which is delayed happens asynchronously using a scheduled thread pool. </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> <strong>Camel 2.4:</strong> Refers to a custom <a shape="rect" href="threading-model.html" title="Threading Model">Thread Pool</a> to be used if <code>asyncDelay</code> has been enabled. </p></td></tr><tr><td colspan="1" rowspan="
1" class="confluenceTd"><p> <code>callerRunsWhenRejected</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.4:</strong> Is used if <code>asyncDelayed</code> was enabled. This controls if the caller thread should execute the task if the thread pool rejected the task. </p></td></tr></tbody></table>
-</div>
-
-<h3 id="BookInOnePage-Examples.9">Examples</h3>
-
-<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="BookInOnePage-Throttler">Throttler</h3><p>The Throttler Pattern allows you to ensure that a specific endpoint does not get overloaded, or that we don't exceed an agreed SLA with some external service.</p><h3 id="BookInOnePage-Options.14">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>maximumRequestsPerPeriod</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Maximum number of requests per period to throttle. This option must be provided as a positive number. Notice, in the XML DSL, from <strong>Camel 2.8</strong> onwards this option is configured using an <a shape="rect" href="expression.html" title="Expression">Expression</a> instead of an attribute. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>timePeriodMillis</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>1000</code> </p></td><td colspan="1" rows
pan="1" class="confluenceTd"><p> The time period in milliseconds, in which the throttler will allow at most <code>maximumRequestsPerPeriod</code> number of messages. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>asyncDelayed</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.4:</strong> If enabled then any messages which is delayed happens asynchronously using a scheduled thread pool. </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> <strong>Camel 2.4:</strong> Refers to a custom <a shape="rect" href="threading-model.html" title="Threading Model">Thread Pool</a> to be used if <code>asyncDelay</code> has been enabled. </p></td></tr><tr><td colspan="1" rowspan="
1" class="confluenceTd"><p> <code>callerRunsWhenRejected</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.4:</strong> Is used if <code>asyncDelayed</code> was enabled. This controls if the caller thread should execute the task if the thread pool rejected the task. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>rejectExecution</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.14:</strong> If this option is true, throttler throws the RejectExecutionException when the request rate exceeds the limit. </p></td></tr></tbody></table>
+</div><h3 id="BookInOnePage-Examples.9">Examples</h3><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("seda:a").throttle(3).timePeriodMillis(10000).to("log:result", "mock:result");
]]></script>
-</div></div>
-
-<p>So the above example will throttle messages all messages received on <strong>seda:a</strong> before being sent to <strong>mock:result</strong> ensuring that a maximum of 3 messages are sent in any 10 second window.</p>
-
-<p>Note that since <code>timePeriodMillis</code> defaults to 1000 milliseconds, just setting the <code>maximumRequestsPerPeriod</code> has the effect of setting the maximum number of requests per second. So to throttle requests at 100 requests per second between two endpoints, it would look more like this...</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("seda:a").throttle(100).to("seda:b");
+</div></div><p>So the above example will throttle messages all messages received on <strong>seda:a</strong> before being sent to <strong>mock:result</strong> ensuring that a maximum of 3 messages are sent in any 10 second window.</p><p>Note that since <code>timePeriodMillis</code> defaults to 1000 milliseconds, just setting the <code>maximumRequestsPerPeriod</code> has the effect of setting the maximum number of requests per second. So to throttle requests at 100 requests per second between two endpoints, it would look more like this...</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("seda:a").throttle(100).to("seda:b");
]]></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/ThrottlerTest.java?view=markup">junit test case</a></p>
-
-<p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong></p>
-<h4 id="BookInOnePage-Camel2.7.xorolder">Camel 2.7.x or older</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</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/ThrottlerTest.java?view=markup">junit test case</a></p><p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong></p><h4 id="BookInOnePage-Camel2.7.xorolder">Camel 2.7.x or older</h4><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[
<route>
<from uri="seda:a" />
@@ -16260,11 +16235,7 @@ from("seda:a").throttle(100).t
</throttle>
</route>
]]></script>
-</div></div>
-
-<h4 id="BookInOnePage-Camel2.8onwards">Camel 2.8 onwards</h4>
-<p>In Camel 2.8 onwards you must set the maximum period as an <a shape="rect" href="expression.html">Expression</a> as shown below where we use a <a shape="rect" href="constant.html">Constant</a> expression:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="BookInOnePage-Camel2.8onwards">Camel 2.8 onwards</h4><p>In Camel 2.8 onwards you must set the maximum period as an <a shape="rect" href="expression.html">Expression</a> as shown below where we use a <a shape="rect" href="constant.html">Constant</a> expression:</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[
<route>
<from uri="seda:a"/>
@@ -16275,12 +16246,7 @@ from("seda:a").throttle(100).t
</throttle>
</route>
]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-Dynamicallychangingmaximumrequestsperperiod">Dynamically changing maximum requests per period</h3>
-<p><strong>Available as of Camel 2.8</strong> <br clear="none">
-Since we use an <a shape="rect" href="expression.html">Expression</a> you can adjust this value at runtime, for example you can provide a header with the value. At runtime Camel evaluates the expression and converts the result to a <code>java.lang.Long</code> type. In the example below we use a header from the message to determine the maximum requests per period. If the header is absent, then the <a shape="rect" href="throttler.html">Throttler</a> uses the old value. So that allows you to only provide a header if the value is to be changed:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookInOnePage-Dynamicallychangingmaximumrequestsperperiod">Dynamically changing maximum requests per period</h3><p><strong>Available as of Camel 2.8</strong> <br clear="none"> Since we use an <a shape="rect" href="expression.html">Expression</a> you can adjust this value at runtime, for example you can provide a header with the value. At runtime Camel evaluates the expression and converts the result to a <code>java.lang.Long</code> type. In the example below we use a header from the message to determine the maximum requests per period. If the header is absent, then the <a shape="rect" href="throttler.html">Throttler</a> uses the old value. So that allows you to only provide a header if the value is to be changed:</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[
<route>
<from uri="direct:expressionHeader"/>
@@ -16291,20 +16257,10 @@ Since we use an <a shape="rect" href="ex
</throttle>
</route>
]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-Asynchronousdelaying">Asynchronous delaying</h3>
-<p><strong>Available as of Camel 2.4</strong></p>
-
-<p>You can let the <a shape="rect" href="throttler.html">Throttler</a> use non blocking asynchronous delaying, which means Camel will use a scheduler to schedule a task to be executed in the future. The task will then continue routing. This allows the caller thread to not block and be able to service other messages, etc.</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("seda:a").throttle(100).asyncDelayed().to("seda:b");
+</div></div><h3 id="BookInOnePage-Asynchronousdelaying">Asynchronous delaying</h3><p><strong>Available as of Camel 2.4</strong></p><p>You can let the <a shape="rect" href="throttler.html">Throttler</a> use non blocking asynchronous delaying, which means Camel will use a scheduler to schedule a task to be executed in the future. The task will then continue routing. This allows the caller thread to not block and be able to service other messages, etc.</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("seda:a").throttle(100).asyncDelayed().to("seda:b");
]]></script>
-</div></div>
-
-<h4 id="BookInOnePage-UsingThisPattern.24">Using This Pattern</h4>
+</div></div><p></p><h4 id="BookInOnePage-UsingThisPattern.24">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>
<h2 id="BookInOnePage-SamplingThrottler">Sampling Throttler</h2>
@@ -20111,11 +20067,11 @@ template.send("direct:alias-verify&
</div>
</div>
<p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1402629519661 {padding: 0px;}
-div.rbtoc1402629519661 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1402629519661 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1402827464072 {padding: 0px;}
+div.rbtoc1402827464072 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1402827464072 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1402629519661">
+/*]]>*/</style></p><div class="toc-macro rbtoc1402827464072">
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>
Modified: websites/production/camel/content/book-pattern-appendix.html
==============================================================================
--- websites/production/camel/content/book-pattern-appendix.html (original)
+++ websites/production/camel/content/book-pattern-appendix.html Sun Jun 15 10:21:12 2014
@@ -1625,7 +1625,7 @@ from("direct:streaming")
.split().tokenizeXML("order", "orders").streaming()
.to("activemq:queue:order");
]]></script>
-</div></div><p><span style="line-height: 1.4285715;">Available as of Camel 2.13.1, you can set the above inheritNamsepaceTagName property to "*" to include the preceding context in each token (i.e., generating each token enclosed in its ancestor elements).</span></p><h4 id="BookPatternAppendix-SplittingfilesbygroupingNlinestogether">Splitting files by grouping N lines together</h4><p><strong>Available as of Camel 2.10</strong></p><p>The <a shape="rect" href="tokenizer.html">Tokenizer</a> language has a new option <code>group</code> that allows you to group N parts together, for example to split big files into chunks of 1000 lines.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p><span style="line-height: 1.4285715;">Available as of Camel 2.13.1, you can set the above inheritNamsepaceTagName property to "*" to include the preceding context in each token (i.e., generating each token enclosed in its ancestor elements). It is noted that each token must share the same ancestor elements in this case.</span></p><h4 id="BookPatternAppendix-SplittingfilesbygroupingNlinestogether">Splitting files by grouping N lines together</h4><p><strong>Available as of Camel 2.10</strong></p><p>The <a shape="rect" href="tokenizer.html">Tokenizer</a> language has a new option <code>group</code> that allows you to group N parts together, for example to split big files into chunks of 1000 lines.</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("file:inbox")
.split().tokenize("\n", 1000).streaming()
.to("activemq:queue:order");
@@ -2956,41 +2956,16 @@ from("direct:c").routingSlip(h
</div></div><h4 id="BookPatternAppendix-FurtherExamples.1">Further Examples</h4><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/routingslip">routing slip test cases</a>.</p><p></p><h4 id="BookPatternAppendix-UsingThisPattern.23">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>
-<h3 id="BookPatternAppendix-Throttler">Throttler</h3>
-
-<p>The Throttler Pattern allows you to ensure that a specific endpoint does not get overloaded, or that we don't exceed an agreed SLA with some external service.</p>
-
-<h3 id="BookPatternAppendix-Options.4">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>maximumRequestsPerPeriod</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Maximum number of requests per period to throttle. This option must be provided as a positive number. Notice, in the XML DSL, from <strong>Camel 2.8</strong> onwards this option is configured using an <a shape="rect" href="expression.html" title="Expression">Expression</a> instead of an attribute. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>timePeriodMillis</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>1000</code> </p></td><td colspan="1" rows
pan="1" class="confluenceTd"><p> The time period in milliseconds, in which the throttler will allow at most <code>maximumRequestsPerPeriod</code> number of messages. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>asyncDelayed</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.4:</strong> If enabled then any messages which is delayed happens asynchronously using a scheduled thread pool. </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> <strong>Camel 2.4:</strong> Refers to a custom <a shape="rect" href="threading-model.html" title="Threading Model">Thread Pool</a> to be used if <code>asyncDelay</code> has been enabled. </p></td></tr><tr><td colspan="1" rowspan="
1" class="confluenceTd"><p> <code>callerRunsWhenRejected</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.4:</strong> Is used if <code>asyncDelayed</code> was enabled. This controls if the caller thread should execute the task if the thread pool rejected the task. </p></td></tr></tbody></table>
-</div>
-
-<h3 id="BookPatternAppendix-Examples.2">Examples</h3>
-
-<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="BookPatternAppendix-Throttler">Throttler</h3><p>The Throttler Pattern allows you to ensure that a specific endpoint does not get overloaded, or that we don't exceed an agreed SLA with some external service.</p><h3 id="BookPatternAppendix-Options.4">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>maximumRequestsPerPeriod</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Maximum number of requests per period to throttle. This option must be provided as a positive number. Notice, in the XML DSL, from <strong>Camel 2.8</strong> onwards this option is configured using an <a shape="rect" href="expression.html" title="Expression">Expression</a> instead of an attribute. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>timePeriodMillis</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>1000</code> </p></td><td colspan="1" rows
pan="1" class="confluenceTd"><p> The time period in milliseconds, in which the throttler will allow at most <code>maximumRequestsPerPeriod</code> number of messages. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>asyncDelayed</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.4:</strong> If enabled then any messages which is delayed happens asynchronously using a scheduled thread pool. </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> <strong>Camel 2.4:</strong> Refers to a custom <a shape="rect" href="threading-model.html" title="Threading Model">Thread Pool</a> to be used if <code>asyncDelay</code> has been enabled. </p></td></tr><tr><td colspan="1" rowspan="
1" class="confluenceTd"><p> <code>callerRunsWhenRejected</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.4:</strong> Is used if <code>asyncDelayed</code> was enabled. This controls if the caller thread should execute the task if the thread pool rejected the task. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>rejectExecution</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.14:</strong> If this option is true, throttler throws the RejectExecutionException when the request rate exceeds the limit. </p></td></tr></tbody></table>
+</div><h3 id="BookPatternAppendix-Examples.2">Examples</h3><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("seda:a").throttle(3).timePeriodMillis(10000).to("log:result", "mock:result");
]]></script>
-</div></div>
-
-<p>So the above example will throttle messages all messages received on <strong>seda:a</strong> before being sent to <strong>mock:result</strong> ensuring that a maximum of 3 messages are sent in any 10 second window.</p>
-
-<p>Note that since <code>timePeriodMillis</code> defaults to 1000 milliseconds, just setting the <code>maximumRequestsPerPeriod</code> has the effect of setting the maximum number of requests per second. So to throttle requests at 100 requests per second between two endpoints, it would look more like this...</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("seda:a").throttle(100).to("seda:b");
+</div></div><p>So the above example will throttle messages all messages received on <strong>seda:a</strong> before being sent to <strong>mock:result</strong> ensuring that a maximum of 3 messages are sent in any 10 second window.</p><p>Note that since <code>timePeriodMillis</code> defaults to 1000 milliseconds, just setting the <code>maximumRequestsPerPeriod</code> has the effect of setting the maximum number of requests per second. So to throttle requests at 100 requests per second between two endpoints, it would look more like this...</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("seda:a").throttle(100).to("seda:b");
]]></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/ThrottlerTest.java?view=markup">junit test case</a></p>
-
-<p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong></p>
-<h4 id="BookPatternAppendix-Camel2.7.xorolder">Camel 2.7.x or older</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</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/ThrottlerTest.java?view=markup">junit test case</a></p><p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong></p><h4 id="BookPatternAppendix-Camel2.7.xorolder">Camel 2.7.x or older</h4><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[
<route>
<from uri="seda:a" />
@@ -2999,11 +2974,7 @@ from("seda:a").throttle(100).t
</throttle>
</route>
]]></script>
-</div></div>
-
-<h4 id="BookPatternAppendix-Camel2.8onwards">Camel 2.8 onwards</h4>
-<p>In Camel 2.8 onwards you must set the maximum period as an <a shape="rect" href="expression.html">Expression</a> as shown below where we use a <a shape="rect" href="constant.html">Constant</a> expression:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="BookPatternAppendix-Camel2.8onwards">Camel 2.8 onwards</h4><p>In Camel 2.8 onwards you must set the maximum period as an <a shape="rect" href="expression.html">Expression</a> as shown below where we use a <a shape="rect" href="constant.html">Constant</a> expression:</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[
<route>
<from uri="seda:a"/>
@@ -3014,12 +2985,7 @@ from("seda:a").throttle(100).t
</throttle>
</route>
]]></script>
-</div></div>
-
-<h3 id="BookPatternAppendix-Dynamicallychangingmaximumrequestsperperiod">Dynamically changing maximum requests per period</h3>
-<p><strong>Available as of Camel 2.8</strong> <br clear="none">
-Since we use an <a shape="rect" href="expression.html">Expression</a> you can adjust this value at runtime, for example you can provide a header with the value. At runtime Camel evaluates the expression and converts the result to a <code>java.lang.Long</code> type. In the example below we use a header from the message to determine the maximum requests per period. If the header is absent, then the <a shape="rect" href="throttler.html">Throttler</a> uses the old value. So that allows you to only provide a header if the value is to be changed:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookPatternAppendix-Dynamicallychangingmaximumrequestsperperiod">Dynamically changing maximum requests per period</h3><p><strong>Available as of Camel 2.8</strong> <br clear="none"> Since we use an <a shape="rect" href="expression.html">Expression</a> you can adjust this value at runtime, for example you can provide a header with the value. At runtime Camel evaluates the expression and converts the result to a <code>java.lang.Long</code> type. In the example below we use a header from the message to determine the maximum requests per period. If the header is absent, then the <a shape="rect" href="throttler.html">Throttler</a> uses the old value. So that allows you to only provide a header if the value is to be changed:</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[
<route>
<from uri="direct:expressionHeader"/>
@@ -3030,20 +2996,10 @@ Since we use an <a shape="rect" href="ex
</throttle>
</route>
]]></script>
-</div></div>
-
-<h3 id="BookPatternAppendix-Asynchronousdelaying">Asynchronous delaying</h3>
-<p><strong>Available as of Camel 2.4</strong></p>
-
-<p>You can let the <a shape="rect" href="throttler.html">Throttler</a> use non blocking asynchronous delaying, which means Camel will use a scheduler to schedule a task to be executed in the future. The task will then continue routing. This allows the caller thread to not block and be able to service other messages, etc.</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("seda:a").throttle(100).asyncDelayed().to("seda:b");
+</div></div><h3 id="BookPatternAppendix-Asynchronousdelaying">Asynchronous delaying</h3><p><strong>Available as of Camel 2.4</strong></p><p>You can let the <a shape="rect" href="throttler.html">Throttler</a> use non blocking asynchronous delaying, which means Camel will use a scheduler to schedule a task to be executed in the future. The task will then continue routing. This allows the caller thread to not block and be able to service other messages, etc.</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("seda:a").throttle(100).asyncDelayed().to("seda:b");
]]></script>
-</div></div>
-
-<h4 id="BookPatternAppendix-UsingThisPattern.24">Using This Pattern</h4>
+</div></div><p></p><h4 id="BookPatternAppendix-UsingThisPattern.24">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>
<h2 id="BookPatternAppendix-SamplingThrottler">Sampling Throttler</h2>
@@ -5237,8 +5193,7 @@ from("direct:start").choice()
<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="BookPatternAppendix-Options.11">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> </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">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">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="conflue
nceTd"><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> </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="BookPatternAppendix-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="BookPatternAppendix-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.h
tml">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="BookPatternAppendix-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="BookPatternAppendix-Options.11">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> </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</co
de> 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">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">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</co
de></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> </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="BookPatternAppendix-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="rec
t" 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="BookPatternAppendix-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 r
un in parallel with the original. Beware 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="BookPatternAppendix-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")
@@ -5396,7 +5351,7 @@ from("direct:tap")
 <route id="moo" xmlns="http://camel.apache.org/schema/spring">
<from uri="direct:moo"/>
- <log message="Me Got ${body}" loggingLevel="INFO loggerRef="myLogger"/>
+ <log message="Me Got ${body}" loggingLevel="INFO" loggerRef="myLogger"/>
<to uri="mock:baz"/>
</route>
]]></script>
Modified: websites/production/camel/content/book-tutorials.html
==============================================================================
--- websites/production/camel/content/book-tutorials.html (original)
+++ websites/production/camel/content/book-tutorials.html Sun Jun 15 10:21:12 2014
@@ -157,11 +157,11 @@ While not actual tutorials you might fin
</div>
</div>
<h2 id="BookTutorials-Preface">Preface</h2><p>This tutorial aims to guide the reader through the stages of creating a project which uses Camel to facilitate the routing of messages from a JMS queue to a <a shape="rect" class="external-link" href="http://www.springramework.org" rel="nofollow">Spring</a> service. The route works in a synchronous fashion returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1400386661234 {padding: 0px;}
-div.rbtoc1400386661234 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1400386661234 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1402827536198 {padding: 0px;}
+div.rbtoc1402827536198 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1402827536198 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1400386661234">
+/*]]>*/</style></p><div class="toc-macro rbtoc1402827536198">
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Preface">Preface</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-About">About</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-CreatetheCamelProject">Create the Camel Project</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-UpdatethePOMwithDependencies">Update the POM with Dependencies</a></li></ul>
</li><li><a shape="rect" href="#Tutorial-JmsRemoting-WritingtheServer">Writing the Server</a>
@@ -2347,11 +2347,11 @@ So we completed the last piece in the pi
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1400386661473 {padding: 0px;}
-div.rbtoc1400386661473 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1400386661473 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1402827536847 {padding: 0px;}
+div.rbtoc1402827536847 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1402827536847 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1400386661473">
+/*]]>*/</style><div class="toc-macro rbtoc1402827536847">
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis 1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Introduction">Introduction</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-SettinguptheprojecttorunAxis">Setting up the project to run Axis</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Maven2">Maven 2</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-wsdl">wsdl</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-ConfiguringAxis">Configuring Axis</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-RunningtheExample">Running the Example</a></li></ul>
Added: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary file - no diff available.
Propchange: websites/production/camel/content/cache/main.pageCache
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: websites/production/camel/content/camel-30-ideas.html
==============================================================================
--- websites/production/camel/content/camel-30-ideas.html (original)
+++ websites/production/camel/content/camel-30-ideas.html Sun Jun 15 10:21:12 2014
@@ -109,11 +109,11 @@
<div class="sectionMacroRow"><div class="columnMacro" style="width:20%;min-width:20%;max-width:20%;">
<div class="panel" style="border-width: 1px;"><div class="panelContent">
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1400055682863 {padding: 0px;}
-div.rbtoc1400055682863 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1400055682863 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1402827511473 {padding: 0px;}
+div.rbtoc1402827511473 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1402827511473 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1400055682863">
+/*]]>*/</style><div class="toc-macro rbtoc1402827511473">
<ul class="toc-indentation"><li><a shape="rect" href="#Camel3.0-Ideas-Camel3.0Ideas">Camel 3.0 Ideas</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Camel3.0-Ideas-Tableofcontents">Table of contents</a></li><li><a shape="rect" href="#Camel3.0-Ideas-JDKsupport">JDK support</a></li><li><a shape="rect" href="#Camel3.0-Ideas-JDK8JavaDSL">JDK8 Java DSL</a></li><li><a shape="rect" href="#Camel3.0-Ideas-RoutingCoreRe-engineering(raulk)">Routing Core Re-engineering (raulk)</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Camel3.0-Ideas-ConvertingsomeEIPsfrom"performers"tomere"deciders"">Converting some EIPs from "performers" to mere "deciders"</a></li></ul>
Modified: websites/production/camel/content/camel-jmx.html
==============================================================================
--- websites/production/camel/content/camel-jmx.html (original)
+++ websites/production/camel/content/camel-jmx.html Sun Jun 15 10:21:12 2014
@@ -87,11 +87,11 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2 id="CamelJMX-CamelJMX">Camel JMX</h2><p>Apache Camel has extensive support for JMX to allow you to monitor and control the Camel managed objects with a JMX client.<br clear="none"> Camel also provides a <a shape="rect" href="jmx.html">JMX</a> component that allows you to subscribe to MBean notifications. This page is about how to manage and monitor Camel using JMX.</p><h3 id="CamelJMX-ActivatingJMXinCamel">Activating JMX in Camel</h3><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1400386657972 {padding: 0px;}
-div.rbtoc1400386657972 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1400386657972 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1402827509339 {padding: 0px;}
+div.rbtoc1402827509339 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1402827509339 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1400386657972">
+/*]]>*/</style></p><div class="toc-macro rbtoc1402827509339">
<ul class="toc-indentation"><li><a shape="rect" href="#CamelJMX-CamelJMX">Camel JMX</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CamelJMX-ActivatingJMXinCamel">Activating JMX in Camel</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CamelJMX-UsingJMXtomanageApacheCamel">Using JMX to manage Apache Camel</a></li><li><a shape="rect" href="#CamelJMX-DisablingJMXinstrumentationagentinCamel">Disabling JMX instrumentation agent in Camel</a></li><li><a shape="rect" href="#CamelJMX-LocatingaMBeanServerintheJavaVM">Locating a MBeanServer in the Java VM</a></li><li><a shape="rect" href="#CamelJMX-CreatingJMXRMIConnectorServer">Creating JMX RMI Connector Server</a></li><li><a shape="rect" href="#CamelJMX-JMXServiceURL">JMX Service URL</a></li><li><a shape="rect" href="#CamelJMX-TheSystemPropertiesforCamelJMXsupport">The System Properties for Camel JMX support</a></li><li><a shape="rect" href="#CamelJMX-HowtouseauthenticationwithJMX">How to use authentication with JMX</a></li><li><a shape="rect" href="#CamelJMX-JMXinsideanApplicationServer">JMX inside an Application Server</a>
Modified: websites/production/camel/content/component.html
==============================================================================
--- websites/production/camel/content/component.html (original)
+++ websites/production/camel/content/component.html Sun Jun 15 10:21:12 2014
@@ -239,7 +239,10 @@ disruptor-vm:someName[?<option>]
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports asynchronous message processing on Google App Engine by using the <a shape="rect" class="external-link" href="http://code.google.com/appengine/docs/java/taskqueue/" rel="nofollow">task queueing service</a> as message queue. See also <a shape="rect" href="gae.html">Camel Components for Google App Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="gmail.html">GMail</a> / <a shape="rect" href="gae.html">camel-gae</a></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[gmail://user@g[oogle]mail.com[?options]
]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports sending of emails via the <a shape="rect" class="external-link" href="http://code.google.com/appengine/docs/java/mail/" rel="nofollow">mail service</a> of Google App Engine. See also <a shape="rect" href="gae.html">Camel Components for Google App Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="geocoder.html">Geocoder</a> / camel-geocoder</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports sending of emails via the <a shape="rect" class="external-link" href="http://code.google.com/appengine/docs/java/mail/" rel="nofollow">mail service</a> of Google App Engine. See also <a shape="rect" href="gae.html">Camel Components for Google App Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="gora.html">Gora</a><span>/ camel-gora</span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[gora:instanceName[?options]
+]]></script>
+</div></div><p><span><br clear="none"></span></p></td><td colspan="1" rowspan="1" class="confluenceTd">Supports to work with NoSQL databases using the <a shape="rect" class="external-link" href="http://gora.apache.org/">Apache Gora</a> framework.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="geocoder.html">Geocoder</a> / camel-geocoder</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[geocoder:<address|latlng:latitude,longitude>[?options]
]]></script>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports looking up geocoders for an address, or reverse lookup geocoders from an address.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="guava-eventbus.html">Google Guava EventBus</a> / camel-guava-eventbus</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -566,7 +569,13 @@ disruptor-vm:someName[?<option>]
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>GPL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For using a db4o datastore as a queue via the <a shape="rect" class="external-link" href="http://www.db4o.com/" rel="nofollow">db4o</a> library</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="esper.html">Esper</a> / camel-esper in <a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">camel-extra</a></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[esper:name
]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>GPL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Working with the <a shape="rect" class="external-link" href="http://esper.codehaus.org" rel="nofollow">Esper Library</a> for Event Stream Processing</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="hibernate.html">Hibernate</a> / camel-hibernate in <a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">camel-extra</a></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>GPL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Working with the <a shape="rect" class="external-link" href="http://esper.codehaus.org" rel="nofollow">Esper Library</a> for Event Stream Processing</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Fabric <a shape="rect" class="external-link" href="http://fabric8.io/gitbook/camelEndpointAmq.html" rel="nofollow">AMQ</a> / mq-fabric-camel in <a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow"></a><a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">f</a><a shape="rect" class="external-link" href="http://fabric8.io/" rel="nofollow">abric8</a></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[amq:[queue|topic:]destinationName]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The <strong><a shape="rect" class="external-link" href="http://fabric8.io/gitbook/camelEndpointAmq.html" rel="nofollow">amq:</a></strong> endpoint works exactly like the <strong>activemq:</strong> endpoint in Apache Camel; only it uses the <a shape="rect" class="external-link" href="http://fabric8.io/" rel="nofollow">fabric</a> to automatically discover the broker. So there is no configuration required; it'll just work out of the box and automatically discover whatever ActiveMQ message brokers are available; with failover and load balancing.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span>Fabric <a shape="rect" class="external-link" href="http://fabric8.io/gitbook/camelEndpointFabric.html" rel="nofollow">Fabric</a></span><span> / fabric-camel in </span><a shape="rect" class="external-link" href="http://code.google.com/p/ca
mel-extra/" rel="nofollow"></a><a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">f</a><a shape="rect" class="external-link" href="http://fabric8.io/" rel="nofollow">abric8</a></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[fabric:logicalName:camelEndpointUri]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd">Apache</td><td colspan="1" rowspan="1" class="confluenceTd">The <strong><a shape="rect" class="external-link" href="http://fabric8.io/gitbook/camelEndpointFabric.html" rel="nofollow">fabric:</a></strong> endpoint uses Fabric's discovery mechanism to expose physical sockets, HTTP endpoints, etc. into the <a shape="rect" class="external-link" href="http://fabric8.io/gitbook/registry.html" rel="nofollow">runtime registry</a> using a logical name so that clients can use the existing Camel <a shape="rect" href="load-balancer.html">Load Balancer</a>.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span>Fabric <a shape="rect" class="external-link" href="http://fabric8.io/gitbook/camelEndpointMaster.html" rel="nofollow">Master</a> / fabric-camel in </span><a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow"></a><a shape="rect" class="external-link" href="http://co
de.google.com/p/camel-extra/" rel="nofollow">f</a><a shape="rect" class="external-link" href="http://fabric8.io/" rel="nofollow">abric8</a></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[master:clusterName:camelEndpointUri]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd">Apache</td><td colspan="1" rowspan="1" class="confluenceTd">The <strong><a shape="rect" class="external-link" href="http://fabric8.io/gitbook/camelEndpointMaster.html" rel="nofollow">master:</a></strong> endpoint provides a way to ensure only a single consumer in a cluster consumes from a given endpoint; with automatic failover if that JVM dies.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="hibernate.html">Hibernate</a> / camel-hibernate in <a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">camel-extra</a></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[hibernate://entityName
]]></script>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>GPL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For using a database as a queue via the <a shape="rect" class="external-link" href="http://www.hibernate.org/" rel="nofollow">Hibernate</a> library</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="jbi.html">JBI</a> / servicemix-camel</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
Modified: websites/production/camel/content/cxf.html
==============================================================================
--- websites/production/camel/content/cxf.html (original)
+++ websites/production/camel/content/cxf.html Sun Jun 15 10:21:12 2014
@@ -99,11 +99,11 @@
</div>
</div>
<p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1400386635002 {padding: 0px;}
-div.rbtoc1400386635002 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1400386635002 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1402827523577 {padding: 0px;}
+div.rbtoc1402827523577 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1402827523577 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1400386635002">
+/*]]>*/</style></p><div class="toc-macro rbtoc1402827523577">
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>
Modified: websites/production/camel/content/scala-dsl-eip.html
==============================================================================
--- websites/production/camel/content/scala-dsl-eip.html (original)
+++ websites/production/camel/content/scala-dsl-eip.html Sun Jun 15 10:21:12 2014
@@ -100,11 +100,11 @@ You can check the <a shape="rect" class=
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1400386656450 {padding: 0px;}
-div.rbtoc1400386656450 ul {list-style: none;margin-left: 0px;}
-div.rbtoc1400386656450 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1402827547494 {padding: 0px;}
+div.rbtoc1402827547494 ul {list-style: none;margin-left: 0px;}
+div.rbtoc1402827547494 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1400386656450">
+/*]]>*/</style><div class="toc-macro rbtoc1402827547494">
<ul class="toc-indentation"><li><span class="TOCOutline">1</span> <a shape="rect" href="#ScalaDSL-EIP-Messagingsystems">Messaging systems</a>
<ul class="toc-indentation"><li><span class="TOCOutline">1.1</span> <a shape="rect" href="#ScalaDSL-EIP-Pipelinepipeline">Pipeline</a></li><li><span class="TOCOutline">1.2</span> <a shape="rect" href="#ScalaDSL-EIP-Filterfilter">Filter</a></li></ul>
</li><li><span class="TOCOutline">2</span> <a shape="rect" href="#ScalaDSL-EIP-Messagingchannels">Messaging channels</a>
Modified: websites/production/camel/content/siteindex.html
==============================================================================
--- websites/production/camel/content/siteindex.html (original)
+++ websites/production/camel/content/siteindex.html Sun Jun 15 10:21:12 2014
@@ -91,7 +91,7 @@
<p>
<table class="grid" width="99%" cellspacing="0"><tr><td colspan="2" rowspan="1">
- <table width="100%"><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-0-9">0-9</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-A">A</a> ... 31</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-B">B</a> ... 38</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-C">C</a> ... 154</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-D">D</a> ... 30</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-E">E</a> ... 29</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-F">F</a> ... 14</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-G">G</a> ... 25</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-H">H</a> ... 83</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-I">I</a> ... 17</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-J">J</a> ... 27</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-K">K</a> ... 3</td></tr><tr><td colspan="1" row
span="1"><a shape="rect" href="#index-L">L</a> ... 17</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-M">M</a> ... 32</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-N">N</a> ... 9</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-O">O</a> ... 6</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-P">P</a> ... 24</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Q">Q</a> ... 5</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-R">R</a> ... 30</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-S">S</a> ... 77</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-T">T</a> ... 42</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-U">U</a> ... 17</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-V">V</a> ... 8</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-W">W</a> ... 30</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-X">X</a> ... 13</td><
td colspan="1" rowspan="1"><a shape="rect" href="#index-Y">Y</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Z">Z</a> ... 4</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-%21@%23%24">!@#$</a> ... 0</td><td colspan="1" rowspan="1"> </td><td colspan="1" rowspan="1"> </td></tr></table>
+ <table width="100%"><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-0-9">0-9</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-A">A</a> ... 31</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-B">B</a> ... 39</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-C">C</a> ... 154</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-D">D</a> ... 30</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-E">E</a> ... 29</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-F">F</a> ... 14</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-G">G</a> ... 26</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-H">H</a> ... 83</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-I">I</a> ... 17</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-J">J</a> ... 27</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-K">K</a> ... 3</td></tr><tr><td colspan="1" row
span="1"><a shape="rect" href="#index-L">L</a> ... 17</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-M">M</a> ... 32</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-N">N</a> ... 9</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-O">O</a> ... 6</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-P">P</a> ... 24</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Q">Q</a> ... 5</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-R">R</a> ... 30</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-S">S</a> ... 77</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-T">T</a> ... 42</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-U">U</a> ... 17</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-V">V</a> ... 8</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-W">W</a> ... 30</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-X">X</a> ... 13</td><
td colspan="1" rowspan="1"><a shape="rect" href="#index-Y">Y</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Z">Z</a> ... 4</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-%21@%23%24">!@#$</a> ... 0</td><td colspan="1" rowspan="1"> </td><td colspan="1" rowspan="1"> </td></tr></table>
</td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-0-9"></a>0-9</h4>
</td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-A"></a>A</h4>
<span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="acknowledgment.html">Acknowledgment</a>
@@ -203,6 +203,9 @@
<span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="banner.html">Banner</a>
<br clear="none">
<div class="smalltext" style="margin: 0 0 0 36px"><div id="asf_logo"> <div id="activemq_logo" style="height:108px; background:transparent url(banner.data/apache-camel-7.png) no-repeat scroll left top;"> <a style="float:left; width:310px;display:block;text-indent:-5000px;text-decoration:none;line-height:1</div>
+ <span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="barcode-data-format.html">Barcode Data Format</a>
+ <br clear="none">
+ <div class="smalltext" style="margin: 0 0 0 36px">Available as of Camel 2.14 The barcode data format is based on the zxing library. The goal of this component is to create a barcode image from a String (marshal) and a String from a barcode image (unmarshal). You're free to use all features that zxing off</div>
<span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="base64.html">Base64</a>
<br clear="none">
<div class="smalltext" style="margin: 0 0 0 36px">Base64 Data Format Available as of Camel 2.11 The Base64 Data Format is a data format for base64 encoding and decoding. Options Option Default Description lineLength 76 To specific a maximum line length for the encoded data. lineSeparator \r\n The line se</div>
@@ -1015,6 +1018,9 @@
<span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="google-summerofcode.html">Google SummerOfCode</a>
<br clear="none">
<div class="smalltext" style="margin: 0 0 0 36px">Ideas for the Apache Sponsored GSoC2009. 2009 Full support of the Camel DSL in Ruby and Python Camel provides an Enterprise Integration Patterns Domain Specific Language which can be used from many languges such as Java, XML, Groovy, Scala. There is suppo</div>
+ <span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="gora.html">Gora</a>
+ <br clear="none">
+ <div class="smalltext" style="margin: 0 0 0 36px">Camel-Gora is an Apache Camel component that allows you to work with NoSQL databases using the Apache Gora framework. Available as of Camel 2.14 Maven users will need to add the following dependency to their pom.xml for this component: <dependency>  <grou</div>
<span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="graceful-shutdown.html">Graceful Shutdown</a>
<br clear="none">
<div class="smalltext" style="margin: 0 0 0 36px">Graceful Shutdown Available as of Camel 2.2 Camel now supports a pluggable shutdown strategy using org.apache.camel.spi.ShutdownStrategy. Its responsible for shutting down routes in a graceful manner. The other resources will still be handled by CamelCont</div>
@@ -2210,7 +2216,7 @@
<div class="smalltext" style="margin: 0 0 0 36px">User Guide If you want to get more familiar with what Apache Camel has to offer, please try the following resources: Wiki pages Getting Started Longer Getting Started Guide Camel jar dependencies Working with Camel and Spring Working with Camel and Guice </div>
<span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="user-stories.html">User Stories</a>
<br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">User Stories This page is intended as a place to collect user stories and feedback on Apache Camel. If you are using or have tried Apache Camel please add an entry or comment; or post to the Discussion Forums. Company or Project Description Apache ActiveM</div>
+ <div class="smalltext" style="margin: 0 0 0 36px">User Stories This page is intended as a place to collect user stories and feedback on Apache Camel. If you are using or have tried Apache Camel please add an entry or comment; or post to the Discussion Forums. Company, Product, or Project Description Apac</div>
<span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="uses-commons-logging.html">Uses Commons Logging</a>
<br clear="none">
<div class="smalltext" style="margin: 0 0 0 36px">Camel uses sfl4j which allows you to configure logging via, among others: Log4j Logback JDK Util Logging logging</div>