camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r906267 [1/2] - in /websites/production/camel/content: book-in-one-page.html book-languages-appendix.html cache/main.pageCache el.html
Date Tue, 15 Apr 2014 09:20:54 GMT
Author: buildbot
Date: Tue Apr 15 09:20:54 2014
New Revision: 906267

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/book-languages-appendix.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/el.html

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 Tue Apr 15 09:20:54 2014
@@ -4185,11 +4185,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.rbtoc1397074885577 {padding: 0px;}
-div.rbtoc1397074885577 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1397074885577 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1397553570155 {padding: 0px;}
+div.rbtoc1397553570155 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1397553570155 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1397074885577">
+/*]]>*/</style></p><div class="toc-macro rbtoc1397553570155">
 <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>
@@ -6375,11 +6375,11 @@ So we completed the last piece in the pi
 
 
 <style type="text/css">/*<![CDATA[*/
-div.rbtoc1397074885921 {padding: 0px;}
-div.rbtoc1397074885921 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1397074885921 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1397553570480 {padding: 0px;}
+div.rbtoc1397553570480 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1397553570480 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style><div class="toc-macro rbtoc1397074885921">
+/*]]>*/</style><div class="toc-macro rbtoc1397553570480">
 <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>
@@ -8039,15 +8039,8 @@ from(&quot;seda:a&quot;).setHeader(&quot
 
 <h3 id="BookInOnePage-Dependencies.1">Dependencies</h3>
 <p>The Constant language is part of <strong>camel-core</strong>.</p> 
-<h2 id="BookInOnePage-EL">EL</h2>
-
-<p>Camel supports the unified JSP and JSF Expression Language via the <a shape="rect" class="external-link" href="http://juel.sourceforge.net/" rel="nofollow">JUEL</a> to allow an <a shape="rect" href="expression.html">Expression</a> or <a shape="rect" href="predicate.html">Predicate</a> to be used in the <a shape="rect" href="dsl.html">DSL</a> or <a shape="rect" href="xml-configuration.html">Xml Configuration</a>.</p>
-
-<p>For example you could use EL inside a <a shape="rect" href="message-filter.html">Message Filter</a> in XML</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;route&gt;
+<h2 id="BookInOnePage-EL">EL</h2><p>Camel supports the unified JSP and JSF Expression Language via the <a shape="rect" class="external-link" href="http://juel.sourceforge.net/" rel="nofollow">JUEL</a> to allow an <a shape="rect" href="expression.html">Expression</a> or <a shape="rect" href="predicate.html">Predicate</a> to be used in the <a shape="rect" href="dsl.html">DSL</a> or <a shape="rect" href="xml-configuration.html">Xml Configuration</a>.</p><p>For example you could use EL inside a <a shape="rect" href="message-filter.html">Message Filter</a> in XML</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;route&gt;
   &lt;from uri=&quot;seda:foo&quot;/&gt;
   &lt;filter&gt;
     &lt;el&gt;${in.headers.foo == &#39;bar&#39;}&lt;/el&gt;
@@ -8055,13 +8048,8 @@ from(&quot;seda:a&quot;).setHeader(&quot
   &lt;/filter&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<p>You could also use slightly different syntax, e.g. if the header name is not a valid identifier:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;route&gt;
+</div></div><p>You could also use slightly different syntax, e.g. if the header name is not a valid identifier:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;route&gt;
   &lt;from uri=&quot;seda:foo&quot;/&gt;
   &lt;filter&gt;
     &lt;el&gt;${in.headers[&#39;My Header&#39;] == &#39;bar&#39;}&lt;/el&gt;
@@ -8069,40 +8057,17 @@ from(&quot;seda:a&quot;).setHeader(&quot
   &lt;/filter&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<p>You could use EL to create an <a shape="rect" href="predicate.html">Predicate</a> in a <a shape="rect" href="message-filter.html">Message Filter</a> or as an <a shape="rect" href="expression.html">Expression</a> for a <a shape="rect" href="recipient-list.html">Recipient List</a></p>
-
-<h3 id="BookInOnePage-Variables">Variables</h3>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Variable </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> exchange </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Exchange </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> the Exchange object </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> in </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Message </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> the exchange.in message </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> out </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Message </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> the exchange.out message </p></td></tr></tbody></table></d
 iv>
-
-
-<h3 id="BookInOnePage-Samples">Samples</h3>
-<p>You can use EL dot notation to invoke operations. If you for instance have a body that contains a POJO that has a <code>getFamiliyName</code> method then you can construct the syntax as follows:</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[
-&quot;$in.body.familyName&quot;
+</div></div><p>You could use EL to create an <a shape="rect" href="predicate.html">Predicate</a> in a <a shape="rect" href="message-filter.html">Message Filter</a> or as an <a shape="rect" href="expression.html">Expression</a> for a <a shape="rect" href="recipient-list.html">Recipient List</a></p><h3 id="BookInOnePage-Variables">Variables</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Variable</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Exchange</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the Exchange object</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>in</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message</p></td><td colspan="
 1" rowspan="1" class="confluenceTd"><p>the exchange.in message</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>out</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the exchange.out message</p></td></tr></tbody></table></div><h3 id="BookInOnePage-Samples">Samples</h3><p>You can use EL dot notation to invoke operations. If you for instance have a body that contains a POJO that has a <code>getFamiliyName</code> method then you can construct the syntax as follows:</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[&quot;${in.body.familyName}&quot;
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-Dependencies.2">Dependencies</h3>
-
-<p>To use EL in your camel routes you need to add the a dependency on <strong>camel-juel</strong> which implements the EL language. </p>
-
-<p>If you use maven you could just add the following to your pom.xml, substituting the version number for the latest &amp; greatest release (see <a shape="rect" href="download.html">the download page for the latest versions</a>).</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;dependency&gt;
+</div></div><h3 id="BookInOnePage-Dependencies.2">Dependencies</h3><p>To use EL in your camel routes you need to add the a dependency on <strong>camel-juel</strong> which implements the EL language.</p><p>If you use maven you could just add the following to your pom.xml, substituting the version number for the latest &amp; greatest release (see <a shape="rect" href="download.html">the download page for the latest versions</a>).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
   &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
   &lt;artifactId&gt;camel-juel&lt;/artifactId&gt;
   &lt;version&gt;x.x.x&lt;/version&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div>
-
-<p>Otherwise you'll also need to include <a shape="rect" class="external-link" href="http://repo2.maven.org/maven2/de/odysseus/juel/juel/2.1.3/juel-2.1.3.jar" rel="nofollow">JUEL</a>.</p>
+</div></div><p>Otherwise you'll also need to include <a shape="rect" class="external-link" href="http://repo2.maven.org/maven2/de/odysseus/juel/juel/2.1.3/juel-2.1.3.jar" rel="nofollow">JUEL</a>.</p>
 <h2 id="BookInOnePage-HeaderExpressionLanguage">Header Expression Language</h2>
 
 <p>The Header Expression Language allows you to extract values of named headers.</p>
@@ -17628,44 +17593,20 @@ from(&quot;seda:b&quot;).delay(1000).to(
 </div></div><p></p><h4 id="BookInOnePage-UsingThisPattern.26">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-SeeAlso.12">See Also</h3><ul><li><a shape="rect" href="delay-interceptor.html">Delay Interceptor</a></li></ul>
-<h3 id="BookInOnePage-LoadBalancer">Load Balancer</h3>
-
-<p>The Load Balancer Pattern allows you to delegate to one of a number of endpoints using a variety of different load balancing policies.</p>
-
-<h3 id="BookInOnePage-Built-inloadbalancingpolicies">Built-in load balancing policies</h3>
-
-<p>Camel provides the following policies out-of-the-box:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Policy </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/loadbalancer/RoundRobinLoadBalancer.html">Round Robin</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The exchanges are selected from in a round robin fashion. This is a well known and classic policy, which spreads the load evenly. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/loadbalancer/RandomLoadBalancer.html">Random</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A random endpoint is selected for each
  exchange. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/loadbalancer/StickyLoadBalancer.html">Sticky</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sticky load balancing using an Expression to calculate a correlation key to perform the sticky load balancing; rather like jsessionid in the web or JMSXGroupID in JMS. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/loadbalancer/TopicLoadBalancer.html">Topic</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Topic which sends to all destinations (rather like JMS Topics) </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://camel.apache.or
 g/maven/current/camel-core/apidocs/org/apache/camel/processor/loadbalancer/FailOverLoadBalancer.html">Failover</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> In case of failures the exchange will be tried on the next endpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Weighted Round-Robin </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5:</strong> The weighted load balancing policy allows you to specify a processing load distribution ratio for each server with respect to the others.  In addition to the weight, endpoint selection is then further refined using <strong>round-robin</strong> distribution based on weight. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Weighted Random </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5:</strong> The weighted load balancing policy allows you to specify a processing load distribution ratio for each server with res
 pect to others.In addition to the weight, endpoint selection is then further refined using <strong>random</strong> distribution based on weight. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Custom </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> From Camel 2.8 onwards the preferred way of using a custom <a shape="rect" href="load-balancer.html">Load Balancer</a> is to use this policy, instead of using the @deprecated <code>ref</code> attribute. </p></td></tr></tbody></table></div>
-
-
-    <div class="aui-message success shadowed information-macro">
+<h3 id="BookInOnePage-LoadBalancer">Load Balancer</h3><p>The Load Balancer Pattern allows you to delegate to one of a number of endpoints using a variety of different load balancing policies.</p><h3 id="BookInOnePage-Built-inloadbalancingpolicies">Built-in load balancing policies</h3><p>Camel provides the following policies out-of-the-box:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Policy</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/loadbalancer/RoundRobinLoadBalancer.html">Round Robin</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The exchanges are selected from in a round robin fashion. This is a well known and classic policy, which spreads the load evenly.</p></td></
 tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/loadbalancer/RandomLoadBalancer.html">Random</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A random endpoint is selected for each exchange.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/loadbalancer/StickyLoadBalancer.html">Sticky</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sticky load balancing using an Expression to calculate a correlation key to perform the sticky load balancing; rather like jsessionid in the web or JMSXGroupID in JMS.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apac
 he/camel/processor/loadbalancer/TopicLoadBalancer.html">Topic</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Topic which sends to all destinations (rather like JMS Topics)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/loadbalancer/FailOverLoadBalancer.html">Failover</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>In case of failures the exchange will be tried on the next endpoint.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Weighted Round-Robin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.5:</strong> The weighted load balancing policy allows you to specify a processing load distribution ratio for each server with respect to the others. In addition to the weight, endpoint selection is then further refined using <strong>round-robin</strong> distribu
 tion based on weight.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Weighted Random</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.5:</strong> The weighted load balancing policy allows you to specify a processing load distribution ratio for each server with respect to others.In addition to the weight, endpoint selection is then further refined using <strong>random</strong> distribution based on weight.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Custom</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.8:</strong> From Camel 2.8 onwards the preferred way of using a custom <a shape="rect" href="load-balancer.html">Load Balancer</a> is to use this policy, instead of using the @deprecated <code>ref</code> attribute.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Circuit Breaker</td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.14:</strong> Imple
 ments the&#160;Circuit Breaker pattern as described in "Release it!" book.</p></td></tr></tbody></table></div>    <div class="aui-message success shadowed information-macro">
                     <p class="title">Load balancing HTTP endpoints</p>
                             <span class="aui-icon icon-success">Icon</span>
                 <div class="message-content">
-                            
-<p>If you are proxying and load balancing HTTP, then see <a shape="rect" href="how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html">this page</a> for more details.</p>
+                            <p>If you are proxying and load balancing HTTP, then see <a shape="rect" href="how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html">this page</a> for more details.</p>
                     </div>
     </div>
-
-
-<h3 id="BookInOnePage-RoundRobin">Round Robin</h3>
-
-<p>The round robin load balancer is not meant to work with failover, for that you should use the dedicated <strong>failover</strong> load balancer. The round robin load balancer will only change to next endpoint per message.</p>
-
-<p>The round robin load balancer is stateful as it keeps state of which endpoint to use next time.</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">
+<h3 id="BookInOnePage-RoundRobin">Round Robin</h3><p>The round robin load balancer is not meant to work with failover, for that you should use the dedicated <strong>failover</strong> load balancer. The round robin load balancer will only change to next endpoint per message.</p><p>The round robin load balancer is stateful as it keeps state of which endpoint to use next time.</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[
 from(&quot;direct:start&quot;).loadBalance().
 roundRobin().to(&quot;mock:x&quot;, &quot;mock:y&quot;, &quot;mock:z&quot;);
 ]]></script>
-</div></div>
-
-<p><strong>Using the Spring configuration</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;camelContext id=&quot;camel&quot; xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
+</div></div><p><strong>Using the Spring configuration</strong></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;camelContext id=&quot;camel&quot; xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
   &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
     &lt;loadBalance&gt;        
@@ -17677,47 +17618,21 @@ roundRobin().to(&quot;mock:x&quot;, &quo
   &lt;/route&gt;
 &lt;/camelContext&gt;
 ]]></script>
-</div></div>
-
-<p>The above example loads balance requests from <strong>direct:start</strong> to one of the available <strong>mock endpoint</strong> instances, in this case using a round robin policy.<br clear="none">
-For further examples of this pattern look at <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/RoundRobinLoadBalanceTest.java?view=markup">this junit test case</a></p>
-
-<h3 id="BookInOnePage-Failover">Failover</h3>
-<p>The <code>failover</code> load balancer is capable of trying the next processor in case an <a shape="rect" href="exchange.html">Exchange</a> failed with an <code>exception</code> during processing.<br clear="none">
-You can constrain the <code>failover</code> to activate only when one exception of a list you specify occurs. If you do not specify a list any exception will cause fail over to occur.  This balancer uses the same strategy for matching exceptions as the <a shape="rect" href="exception-clause.html">Exception Clause</a> does for the <strong>onException</strong>.</p>
-
-    <div class="aui-message hint shadowed information-macro">
+</div></div><p>The above example loads balance requests from <strong>direct:start</strong> to one of the available <strong>mock endpoint</strong> instances, in this case using a round robin policy.<br clear="none"> For further examples of this pattern look at <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/RoundRobinLoadBalanceTest.java?view=markup">this junit test case</a></p><h3 id="BookInOnePage-Failover">Failover</h3><p>The <code>failover</code> load balancer is capable of trying the next processor in case an <a shape="rect" href="exchange.html">Exchange</a> failed with an <code>exception</code> during processing.<br clear="none"> You can constrain the <code>failover</code> to activate only when one exception of a list you specify occurs. If you do not specify a list any exception will cause fail over to occur. This balancer uses the same strategy for matching exceptions as the <a shape="rec
 t" href="exception-clause.html">Exception Clause</a> does for the <strong>onException</strong>.</p>    <div class="aui-message hint shadowed information-macro">
                     <p class="title">Enable stream caching if using streams</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">
-                            
-<p>If you use streaming then you should enable <a shape="rect" href="stream-caching.html">Stream Caching</a> when using the failover load balancer. This is needed so the stream can be re-read after failing over to the next processor.</p>
+                            <p>If you use streaming then you should enable <a shape="rect" href="stream-caching.html">Stream caching</a> when using the failover load balancer. This is needed so the stream can be re-read after failing over to the next processor.</p>
                     </div>
     </div>
-
-
-<p>Failover offers the following options:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Option </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inheritErrorHandler </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> boolean </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> Whether or not the <a shape="rect" href="error-handler.html">Error Handler</a> configured on the route should be used. Disable this if you want failover to transfer immediately to the next endpoint. On the other hand, if you have this option enabled, then Camel will first let the <a shape="rect" href="error-handler.html">Error Handler</a> t
 ry to process the message. The <a shape="rect" href="error-handler.html">Error Handler</a> may have been configured to redeliver and use delays between attempts. If you have enabled a number of redeliveries then Camel will try to redeliver to the <strong>same</strong> endpoint, and only fail over to the next endpoint, when the <a shape="rect" href="error-handler.html">Error Handler</a> is exhausted. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumFailoverAttempts </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> int </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> -1 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> A value to indicate after X failover attempts we should exhaust (give up). Use -1 to indicate never give up and continuously try to failover. Use 0 to never failover. And use e.g. 3 to failover at most 3 times before giving up. This option can be used whether or not roundRobin 
 is enabled or not. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> roundRobin </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> boolean </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> Whether or not the <code>failover</code> load balancer should operate in round robin mode or not. If not, then it will <strong>always</strong> start from the first endpoint when a new message is to be processed. In other words it restart from the top for every message. If round robin is enabled, then it keeps state and will continue with the next endpoint in a round robin fashion. When using round robin it will not <em>stick</em> to last known good endpoint, it will always pick the next endpoint to use. </p></td></tr></tbody></table></div>
-
-
-<p><strong>Camel 2.2 or older behavior</strong><br clear="none">
-The current implementation of failover load balancer uses simple logic which <strong>always</strong> tries the first endpoint, and in case of an exception being thrown it tries the next in the list, and so forth. It has no state, and the next message will thus <strong>always</strong> start with the first endpoint.</p>
-
-<p><strong>Camel 2.3 onwards behavior</strong><br clear="none">
-The <code>failover</code> load balancer now supports round robin mode, which allows you to failover in a round robin fashion. See the <code>roundRobin</code> option.</p>
-
-    <div class="aui-message warning shadowed information-macro">
+<p>Failover offers the following options:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>inheritErrorHandler</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>boolean</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether or not the <a shape="rect" href="error-handler.html">Error Handler</a> configured on the route should be used. Disable this if you want failover to transfer immediately to the next endpoint. On the other hand, if you have this option enabled, then Camel will first let the <a shape="rect" href="error-han
 dler.html">Error Handler</a> try to process the message. The <a shape="rect" href="error-handler.html">Error Handler</a> may have been configured to redeliver and use delays between attempts. If you have enabled a number of redeliveries then Camel will try to redeliver to the <strong>same</strong> endpoint, and only fail over to the next endpoint, when the <a shape="rect" href="error-handler.html">Error Handler</a> is exhausted.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maximumFailoverAttempts</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>int</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> A value to indicate after X failover attempts we should exhaust (give up). Use -1 to indicate never give up and continuously try to failover. Use 0 to never failover. And use e.g. 3 to failover at most 3 times before giving up. This option can be used whet
 her or not roundRobin is enabled or not.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>roundRobin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>boolean</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether or not the <code>failover</code> load balancer should operate in round robin mode or not. If not, then it will <strong>always</strong> start from the first endpoint when a new message is to be processed. In other words it restart from the top for every message. If round robin is enabled, then it keeps state and will continue with the next endpoint in a round robin fashion. When using round robin it will not <em>stick</em> to last known good endpoint, it will always pick the next endpoint to use.</p></td></tr></tbody></table></div><p><strong>Camel 2.2 or older behavior</strong><br clear="none"> The current implementation of failover load b
 alancer uses simple logic which <strong>always</strong> tries the first endpoint, and in case of an exception being thrown it tries the next in the list, and so forth. It has no state, and the next message will thus <strong>always</strong> start with the first endpoint.</p><p><strong>Camel 2.3 onwards behavior</strong><br clear="none"> The <code>failover</code> load balancer now supports round robin mode, which allows you to failover in a round robin fashion. See the <code>roundRobin</code> option.</p>    <div class="aui-message warning shadowed information-macro">
                     <p class="title">Redelivery must be enabled</p>
                             <span class="aui-icon icon-warning">Icon</span>
                 <div class="message-content">
-                            
-<p>In Camel 2.2 or older the failover load balancer requires you have enabled Camel <a shape="rect" href="error-handler.html">Error Handler</a> to use redelivery. In Camel 2.3 onwards this is not required as such, as you can mix and match. See the <code>inheritErrorHandler</code> option.</p>
+                            <p>In Camel 2.2 or older the failover load balancer requires you have enabled Camel <a shape="rect" href="error-handler.html">Error Handler</a> to use redelivery. In Camel 2.3 onwards this is not required as such, as you can mix and match. See the <code>inheritErrorHandler</code> option.</p>
                     </div>
     </div>
-
-
-<p>Here is a sample to failover only if a <code>IOException</code> related exception was thrown:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<p>Here is a sample to failover only if a <code>IOException</code> related exception was thrown:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // here we will load balance if IOException was thrown
@@ -17727,25 +17642,16 @@ from(&quot;direct:start&quot;)
     .loadBalance().failover(IOException.class)
         .to(&quot;direct:x&quot;, &quot;direct:y&quot;, &quot;direct:z&quot;);
 ]]></script>
-</div></div> 
-
-<p>You can specify multiple exceptions to failover as the option is varargs, for instance:</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[
-// enable redelivery so failover can react
+</div></div><p>You can specify multiple exceptions to failover as the option is varargs, for instance:</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[// enable redelivery so failover can react
 errorHandler(defaultErrorHandler().maximumRedeliveries(5));
 
 from(&quot;direct:foo&quot;).
     loadBalance().failover(IOException.class, MyOtherException.class)
         .to(&quot;direct:a&quot;, &quot;direct:b&quot;);
 ]]></script>
-</div></div>
-
-<h4 id="BookInOnePage-UsingfailoverinSpringDSL">Using failover in Spring DSL</h4>
-<p>Failover can also be used from Spring DSL and you configure it as:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-   &lt;route errorHandlerRef=&quot;myErrorHandler&quot;&gt;
+</div></div><h4 id="BookInOnePage-UsingfailoverinSpringDSL">Using failover in Spring DSL</h4><p>Failover can also be used from Spring DSL and you configure it as:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[   &lt;route errorHandlerRef=&quot;myErrorHandler&quot;&gt;
       &lt;from uri=&quot;direct:foo&quot;/&gt;
       &lt;loadBalance&gt;
           &lt;failover&gt;
@@ -17757,12 +17663,7 @@ from(&quot;direct:foo&quot;).
       &lt;/loadBalance&gt;
     &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<h4 id="BookInOnePage-Usingfailoverinroundrobinmode">Using failover in round robin mode</h4>
-
-<p>An example using Java DSL:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="BookInOnePage-Usingfailoverinroundrobinmode">Using failover in round robin mode</h4><p>An example using Java DSL:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // Use failover load balancer in stateful round robin mode
@@ -17772,10 +17673,7 @@ from(&quot;direct:start&quot;)
     .loadBalance().failover(-1, false, true).
         to(&quot;direct:bad&quot;, &quot;direct:bad2&quot;, &quot;direct:good&quot;, &quot;direct:good2&quot;);
 ]]></script>
-</div></div> 
-
-<p>And the same example using Spring XML:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>And the same example using Spring XML:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -17791,55 +17689,22 @@ from(&quot;direct:start&quot;)
     &lt;/loadBalance&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div> 
-
-    <div class="aui-message success shadowed information-macro">
+</div></div>    <div class="aui-message success shadowed information-macro">
                     <p class="title">Disabled inheritErrorHandler</p>
                             <span class="aui-icon icon-success">Icon</span>
                 <div class="message-content">
-                            
-<p>You can configure <code>inheritErrorHandler=false</code> if you want to failover to the next endpoint as fast as possible. By disabling the <a shape="rect" href="error-handler.html">Error Handler</a> you ensure it does not <em>intervene</em> which allows the <code>failover</code> load balancer to handle failover asap. By also enabling <code>roundRobin</code> mode, then it will keep retrying until it success. You can then configure the <code>maximumFailoverAttempts</code> option to a high value to let it eventually exhaust (give up) and fail.</p>
+                            <p>You can configure <code>inheritErrorHandler=false</code> if you want to failover to the next endpoint as fast as possible. By disabling the <a shape="rect" href="error-handler.html">Error Handler</a> you ensure it does not <em>intervene</em> which allows the <code>failover</code> load balancer to handle failover asap. By also enabling <code>roundRobin</code> mode, then it will keep retrying until it success. You can then configure the <code>maximumFailoverAttempts</code> option to a high value to let it eventually exhaust (give up) and fail.</p>
                     </div>
     </div>
-
-
-<h3 id="BookInOnePage-WeightedRound-RobinandRandomLoadBalancing">Weighted Round-Robin and Random Load Balancing</h3>
-<p><strong>Available as of Camel 2.5</strong></p>
-
-<p>In many enterprise environments where server nodes of unequal processing power &amp; performance characteristics are utilized to host services and processing endpoints, it is frequently necessary to distribute processing load based on their individual server capabilities so that some endpoints are not unfairly burdened with requests. Obviously simple round-robin or random load balancing do not alleviate problems of this nature. A Weighted Round-Robin and/or Weighted Random load balancer can be used to address this problem.</p>
-
-<p>The weighted load balancing policy allows you to specify a processing load distribution ratio for each server with respect to others. You can specify this as a positive processing weight for each server. A larger number indicates that the server can handle a larger load. The weight is utilized to determine the payload distribution ratio to different processing endpoints with respect to others.</p>
-
-    <div class="aui-message success shadowed information-macro">
+<h3 id="BookInOnePage-WeightedRound-RobinandRandomLoadBalancing">Weighted Round-Robin and Random Load Balancing</h3><p><strong>Available as of Camel 2.5</strong></p><p>In many enterprise environments where server nodes of unequal processing power &amp; performance characteristics are utilized to host services and processing endpoints, it is frequently necessary to distribute processing load based on their individual server capabilities so that some endpoints are not unfairly burdened with requests. Obviously simple round-robin or random load balancing do not alleviate problems of this nature. A Weighted Round-Robin and/or Weighted Random load balancer can be used to address this problem.</p><p>The weighted load balancing policy allows you to specify a processing load distribution ratio for each server with respect to others. You can specify this as a positive processing weight for each server. A larger number indicates that the server can handle a larger load. The weight is utilized
  to determine the payload distribution ratio to different processing endpoints with respect to others.</p>    <div class="aui-message success shadowed information-macro">
                     <p class="title">Disabled inheritErrorHandler</p>
                             <span class="aui-icon icon-success">Icon</span>
                 <div class="message-content">
-                            
-<p>As of Camel 2.6, the Weighted Load balancer usage has been further simplified, there is no need to send in distributionRatio as a List&lt;Integer&gt;. It can be simply sent as a delimited String of integer weights separated by a delimiter of choice.</p>
+                            <p>As of Camel 2.6, the Weighted Load balancer usage has been further simplified, there is no need to send in distributionRatio as a List&lt;Integer&gt;. It can be simply sent as a delimited String of integer weights separated by a delimiter of choice.</p>
                     </div>
     </div>
-
-
-<p>The parameters that can be used are</p>
-
-<p><strong>In Camel 2.5</strong></p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Option </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> roundRobin </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> boolean </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The default value for round-robin is false. In the absence of this setting or parameter the load balancing algorithm used is random.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> distributionRatio </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> List&lt;Integer&gt; </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> none </p></td
 ><td colspan="1" rowspan="1" class="confluenceTd"><p> The distributionRatio is a list consisting on integer weights passed in as a parameter. The distributionRatio must match the number of endpoints and/or processors specified in the load balancer list. In Camel 2.5 if endpoints do not match ratios, then a best effort distribution is attempted. </p></td></tr></tbody></table></div>
-
-
-<p><strong>Available In Camel 2.6</strong></p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Option </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> roundRobin </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> boolean </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The default value for round-robin is false. In the absence of this setting or parameter the load balancing algorithm used is random.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> distributionRatio </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> String </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> none </p></td><td colspan=
 "1" rowspan="1" class="confluenceTd"><p> The distributionRatio is a delimited String consisting on integer weights separated by delimiters for example "2,3,5". The distributionRatio must match the number of endpoints and/or processors specified in the load balancer list. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> distributionRatioDelimiter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> String </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> , </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The distributionRatioDelimiter is the delimiter used to specify the distributionRatio. If this attribute is not specified a default delimiter "," is expected as the delimiter used for specifying the distributionRatio. </p></td></tr></tbody></table></div>
-
-
-<h4 id="BookInOnePage-UsingWeightedround-robin&amp;randomloadbalancing">Using Weighted round-robin &amp; random load balancing</h4>
-
-<p><strong>In Camel 2.5</strong></p>
-
-<p>An example using Java DSL:</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[
-ArrayList&lt;integer&gt; distributionRatio = new ArrayList&lt;integer&gt;();
+<p>The parameters that can be used are</p><p><strong>In Camel 2.5</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>roundRobin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>boolean</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The default value for round-robin is false. In the absence of this setting or parameter the load balancing algorithm used is random.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>distributionRatio</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>List&lt;Integer&gt;</p></td><td col
 span="1" rowspan="1" class="confluenceTd"><p>none</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The distributionRatio is a list consisting on integer weights passed in as a parameter. The distributionRatio must match the number of endpoints and/or processors specified in the load balancer list. In Camel 2.5 if endpoints do not match ratios, then a best effort distribution is attempted.</p></td></tr></tbody></table></div><p><strong>Available In Camel 2.6</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>roundRobin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>boolean</p></td><td colspan="1" rowspan="1"
  class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The default value for round-robin is false. In the absence of this setting or parameter the load balancing algorithm used is random.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>distributionRatio</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>none</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The distributionRatio is a delimited String consisting on integer weights separated by delimiters for example "2,3,5". The distributionRatio must match the number of endpoints and/or processors specified in the load balancer list.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>distributionRatioDelimiter</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>,</p></td><td colspan="1" rowspan="1" cl
 ass="confluenceTd"><p>The distributionRatioDelimiter is the delimiter used to specify the distributionRatio. If this attribute is not specified a default delimiter "," is expected as the delimiter used for specifying the distributionRatio.</p></td></tr></tbody></table></div><h4 id="BookInOnePage-UsingWeightedround-robin&amp;randomloadbalancing">Using Weighted round-robin &amp; random load balancing</h4><p><strong>In Camel 2.5</strong></p><p>An example using Java DSL:</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[ArrayList&lt;integer&gt; distributionRatio = new ArrayList&lt;integer&gt;();
 distributionRatio.add(4);
 distributionRatio.add(2);
 distributionRatio.add(1);
@@ -17854,12 +17719,8 @@ from(&quot;direct:start&quot;)
     .loadBalance().weighted(false, distributionRatio)
     .to(&quot;mock:x&quot;, &quot;mock:y&quot;, &quot;mock:z&quot;);
 ]]></script>
-</div></div>
-
-<p>And the same example using Spring XML:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-    &lt;route&gt;
+</div></div><p>And the same example using Spring XML:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[    &lt;route&gt;
       &lt;from uri=&quot;direct:start&quot;/&gt;
       &lt;loadBalance&gt;
         &lt;weighted roundRobin=&quot;false&quot; distributionRatio=&quot;4 2 1&quot;/&gt;
@@ -17869,14 +17730,8 @@ from(&quot;direct:start&quot;)
       &lt;/loadBalance&gt;
     &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<p><strong>Available In Camel 2.6</strong></p>
-
-<p>An example using Java DSL:</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[
-// round-robin
+</div></div><p><strong>Available In Camel 2.6</strong></p><p>An example using Java DSL:</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[// round-robin
 from(&quot;direct:start&quot;)
     .loadBalance().weighted(true, &quot;4:2:1&quot; distributionRatioDelimiter=&quot;:&quot;)
     .to(&quot;mock:x&quot;, &quot;mock:y&quot;, &quot;mock:z&quot;);
@@ -17886,12 +17741,8 @@ from(&quot;direct:start&quot;)
     .loadBalance().weighted(false, &quot;4,2,1&quot;)
     .to(&quot;mock:x&quot;, &quot;mock:y&quot;, &quot;mock:z&quot;);
 ]]></script>
-</div></div>
-
-<p>And the same example using Spring XML:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-    &lt;route&gt;
+</div></div><p>And the same example using Spring XML:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[    &lt;route&gt;
       &lt;from uri=&quot;direct:start&quot;/&gt;
       &lt;loadBalance&gt;
         &lt;weighted roundRobin=&quot;false&quot; distributionRatio=&quot;4-2-1&quot; distributionRatioDelimiter=&quot;-&quot; /&gt;
@@ -17901,25 +17752,14 @@ from(&quot;direct:start&quot;)
       &lt;/loadBalance&gt;
     &lt;/route&gt;
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-CustomLoadBalancer">Custom Load Balancer</h3>
-
-<p>You can use a custom load balancer (eg your own implementation) also. </p>
-
-<p>An example using Java DSL:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookInOnePage-CustomLoadBalancer">Custom Load Balancer</h3><p>You can use a custom load balancer (eg your own implementation) also.</p><p>An example using Java DSL:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // using our custom load balancer
     .loadBalance(new MyLoadBalancer())
     .to(&quot;mock:x&quot;, &quot;mock:y&quot;, &quot;mock:z&quot;);
 ]]></script>
-</div></div> 
-
-<p>And the same example using XML DSL:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>And the same example using XML DSL:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;!-- this is the implementation of our custom load balancer --&gt;
 &lt;bean id=&quot;myBalancer&quot; class=&quot;org.apache.camel.processor.CustomLoadBalanceTest$MyLoadBalancer&quot;/&gt;
@@ -17938,22 +17778,15 @@ from(&quot;direct:start&quot;)
   &lt;/route&gt;
 &lt;/camelContext&gt;
 ]]></script>
-</div></div> 
-
-<p>Notice in the XML DSL above we use &lt;custom&gt; which is only available in <strong>Camel 2.8</strong> onwards. In older releases you would have to do as follows instead:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-      &lt;loadBalance ref=&quot;myBalancer&quot;&gt;
+</div></div><p>Notice in the XML DSL above we use &lt;custom&gt; which is only available in <strong>Camel 2.8</strong> onwards. In older releases you would have to do as follows instead:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[      &lt;loadBalance ref=&quot;myBalancer&quot;&gt;
         &lt;!-- these are the endpoints to balancer --&gt;
         &lt;to uri=&quot;mock:x&quot;/&gt;
         &lt;to uri=&quot;mock:y&quot;/&gt;
         &lt;to uri=&quot;mock:z&quot;/&gt;
       &lt;/loadBalance&gt;
 ]]></script>
-</div></div>
-
-<p>To implement a custom load balancer you can extend some support classes such as <code>LoadBalancerSupport</code> and <code>SimpleLoadBalancerSupport</code>. The former supports the asynchronous routing engine, and the latter does not. Here is an example:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Custom load balancer implementation</b></div><div class="codeContent panelContent pdl">
+</div></div><p>To implement a custom load balancer you can extend some support classes such as <code>LoadBalancerSupport</code> and <code>SimpleLoadBalancerSupport</code>. The former supports the asynchronous routing engine, and the latter does not. Here is an example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Custom load balancer implementation</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 public static class MyLoadBalancer extends LoadBalancerSupport {
 
@@ -17975,10 +17808,25 @@ public static class MyLoadBalancer exten
     }
 }
 ]]></script>
-</div></div> 
-
-
-<h4 id="BookInOnePage-UsingThisPattern.27">Using This Pattern</h4>
+</div></div><h3 id="BookInOnePage-CircuitBreaker">Circuit Breaker</h3><p>The Circuit Breaker load balancer is a stateful pattern that monitors all calls for certain exceptions. Initially the Circuit Breaker is in closed state and passes all messages. If the are failures and the threshold is reached, it moves to open state and rejects all calls until halfOpenAfter timeout is reached. After this timeout is reached, if there is a new call, it will pass and if the result is success the Circuit Breaker will move to closed state, or to open state if there was an error.</p><p>An example using Java DSL:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from(&quot;direct:start&quot;).loadBalance()
+	.circuitBreaker(2, 1000L, MyCustomException.class)
+    .to(&quot;mock:result&quot;);
+]]></script>
+</div></div><p>And the same example using Spring XML:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;camelContext id=&quot;camel&quot; xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
+	&lt;route&gt;
+    &lt;from uri=&quot;direct:start&quot;/&gt;
+    &lt;loadBalance&gt;
+        &lt;circuitBreaker threshold=&quot;2&quot; halfOpenAfter=&quot;1000&quot;&gt;
+            &lt;exception&gt;MyCustomException&lt;/exception&gt;
+        &lt;/circuitBreaker&gt;
+        &lt;to uri=&quot;mock:result&quot;/&gt;
+    &lt;/loadBalance&gt;
+&lt;/route&gt;
+&lt;/camelContext&gt;
+]]></script>
+</div></div><p></p><h4 id="BookInOnePage-UsingThisPattern.27">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-Multicast">Multicast</h3>
@@ -21506,11 +21354,11 @@ template.send(&quot;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.rbtoc1397074895367 {padding: 0px;}
-div.rbtoc1397074895367 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1397074895367 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1397553585557 {padding: 0px;}
+div.rbtoc1397553585557 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1397553585557 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1397074895367">
+/*]]>*/</style></p><div class="toc-macro rbtoc1397553585557">
 <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>
@@ -27293,7 +27141,7 @@ from(&quot;timer://foo?period=60000&quot
 ]]></script>
 </div></div><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p><h3 id="BookInOnePage-Options.47">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>sessionSupport</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether to enable the session manager on the server side of Jetty. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClient.XXX</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Configuration of Jetty's <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Tutorial/HttpClient" rel="nofollow">HttpClient</a>. For example, setting <code>httpClien
 t.idleTimeout=30000</code> sets the idle timeout to 30 seconds. And <code>httpClient.timeout=30000</code> sets the request timeout to 30 seconds, in case you want to timeout sooner if you have long running request/response calls. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClient</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a shared <code>org.eclipse.jetty.client.HttpClient</code> for all producers created by this endpoint. This option should only be used in special circumstances. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientMinThreads</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong>: To set a value for minimum number of threads in <code>H
 ttpClient</code> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. If not set it default to min 8 threads used in Jettys thread pool. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientMaxThreads</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong>: To set a value for maximum number of threads in <code>HttpClient</code> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. If not set it default to max 254 threads used in Jettys thread pool. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpBindingRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td cols
 pan="1" rowspan="1" class="confluenceTd"><p> Reference to an <code>org.apache.camel.component.http.HttpBinding</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <code>HttpBinding</code> can be used to customize how a response should be written for the consumer. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>jettyHttpBindingRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6.0+:</strong> Reference to an <code>org.apache.camel.component.jetty.JettyHttpBinding</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <code>JettyHttpBinding</code> can be used to customize how a response should be written for the producer. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>matchOnUriPrefix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <co
 de>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Whether or not the <code>CamelServlet</code> should try to find a target consumer by matching the URI prefix if no exact match is found. See here <a shape="rect" href="how-do-i-let-jetty-match-wildcards.html" title="How do I let Jetty match wildcards">How do I let Jetty match wildcards</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>handlers</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies a comma-delimited set of <code>org.mortbay.jetty.Handler</code> instances in your <a shape="rect" href="registry.html" title="Registry">Registry</a> (such as your Spring <code>ApplicationContext</code>). These handlers are added to the Jetty servlet context (for example, to add security). <strong>Important:</strong> You can not use different handlers with different Jetty endpoint
 s using the same port number. The handlers is associated to the port number. If you need different handlers, then use different port numbers. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>chunked</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.2:</strong> If this option is false Jetty servlet will disable the HTTP streaming and set the content-length header on the response </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>enableJmx</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.3:</strong> If this option is true, Jetty JMX support will be enabled for this endpoint. See <a shape="rect" href="#BookInOnePage-JettyJMXsupport">Jetty JMX support</a> for more details. </p></td></tr><tr><td colspan="1"
  rowspan="1" class="confluenceTd"><p> <code>disableStreamCache</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.3:</strong> Determines whether or not the raw input stream from Jetty is cached or not (Camel will read the stream into a in memory/overflow to file, <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a>) cache. By default Camel will cache the Jetty input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to <code>true</code> when you for example need to access the raw stream, such as streaming it directly to a file or other persistent store. DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is <code>false</code> to support reading the stream multiple times. If you use <a shape="
 rect" href="jetty.html" title="Jetty">Jetty</a> to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>throwExceptionOnFailure</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Option to disable throwing the <code>HttpOperationFailedException</code> in case of failed responses from the remote server. This allows you to get all responses regardles of the HTTP status code. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transferException</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.6:</strong>  If enabled and an <a shape="rect" href="exchange.html" title="Exchange">E
 xchange</a> failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a <code>application/x-java-serialized-object</code> content type. On the producer side the exception will be deserialized and thrown as is, instead of the <code>HttpOperationFailedException</code>. The caused exception is required to be serialized. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bridgeEndpoint</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.1:</strong> If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the <strong>throwExceptionOnFailure</strong> to be false to let the HttpProducer send all the fault response back. <br clear="none" class="atl-forced-newline">
-<strong>Camel 2.3:</strong> If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". Also consider setting <strong>disableStreamCache</strong> to true to optimize when bridging. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>enableMultipartFilter</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.5:</strong> Whether Jetty <code>org.eclipse.jetty.servlets.MultiPartFilter</code> is enabled or not. You should set this value to <code>false</code> when bridging endpoints, to ensure multipart requests is proxied/bridged as well. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>multipartFilterRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:
 </strong> Allows using a custom multipart filter. Note: setting <code>multipartFilterRef</code> forces the value of <code>enableMultipartFilter</code> to <code>true</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>filtersRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9:</strong> Allows using a custom filters which is putted into a list and can be find in the <a shape="rect" href="registry.html" title="Registry">Registry</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>continuationTimeout</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:</strong> Allows to set a timeout in millis when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> as consumer (server). By default Je
 tty uses 30000. You can use a value of <code>&lt;= 0</code> to never expire. If a timeout occurs then the request will be expired and Jetty will return back a http error 503 to the client. This option is only in use when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> with the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>useContinuation</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.6:</strong> Whether or not to use <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Feature/Continuations" rel="nofollow">Jetty continuations</a> for the Jetty Server. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslContextParametersRef</code><br clear="none" clas
 s="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code><br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> Reference to a <code>org.apache.camel.util.jsse.SSLContextParameters</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>.&#160; This reference overrides any configured SSLContextParameters at the component level.&#160; See <a shape="rect" href="#BookInOnePage-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>traceEnabled</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether to enable HTTP TRACE for this Jetty consumer. By default TRACE is turned off. </p></td></tr><tr><td colspan="1" rowspan="1" class="confl
 uenceTd"><p> <code>headerFilterStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> Reference to a instance of <code>org.apache.camel.spi.HeaderFilterStrategy</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. It will be used to apply the custom headerFilterStrategy on the new create HttpJettyEndpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>urlRewrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> Refers to a custom <code>org.apache.camel.component.http.UrlRewrite</code> which allows you to rewrite urls when you bridge/proxy endpoints. See more details at <a shape="rect" href="urlrewrite.html" title="UrlRewrite">UrlRewrite</
 a> and <a shape="rect" href="how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html" title="How to use Camel as a HTTP proxy between a client and server">How to use Camel as a HTTP proxy between a client and server</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>responseBufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12:</strong> To use a custom buffer size on the <code>javax.servlet.ServletResponse</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> The http proxy Host url which will be used by Jetty client. </p></td></tr><tr><td colspan="1" rowspan="1" class="conf
 luenceTd"><p> <code>proxyPort</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> The http proxy port which will be used by Jetty client. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> {{sendServerVersion</p></td><th colspan="1" rowspan="1" class="confluenceTh"><p>&#160;</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.13:</strong> if the option is true, jetty will send the server header with the jetty version information to the client which sends the request. </p></td></tr></tbody></table>
+<strong>Camel 2.3:</strong> If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". Also consider setting <strong>disableStreamCache</strong> to true to optimize when bridging. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>enableMultipartFilter</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.5:</strong> Whether Jetty <code>org.eclipse.jetty.servlets.MultiPartFilter</code> is enabled or not. You should set this value to <code>false</code> when bridging endpoints, to ensure multipart requests is proxied/bridged as well. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>multipartFilterRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:
 </strong> Allows using a custom multipart filter. Note: setting <code>multipartFilterRef</code> forces the value of <code>enableMultipartFilter</code> to <code>true</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>filtersRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9:</strong> Allows using a custom filters which is putted into a list and can be find in the <a shape="rect" href="registry.html" title="Registry">Registry</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>continuationTimeout</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:</strong> Allows to set a timeout in millis when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> as consumer (server). By default Je
 tty uses 30000. You can use a value of <code>&lt;= 0</code> to never expire. If a timeout occurs then the request will be expired and Jetty will return back a http error 503 to the client. This option is only in use when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> with the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>useContinuation</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.6:</strong> Whether or not to use <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Feature/Continuations" rel="nofollow">Jetty continuations</a> for the Jetty Server. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslContextParametersRef</code><br clear="none" clas
 s="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code><br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> Reference to a <code>org.apache.camel.util.jsse.SSLContextParameters</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>.&#160; This reference overrides any configured SSLContextParameters at the component level.&#160; See <a shape="rect" href="#BookInOnePage-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>traceEnabled</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether to enable HTTP TRACE for this Jetty consumer. By default TRACE is turned off. </p></td></tr><tr><td colspan="1" rowspan="1" class="confl
 uenceTd"><p> <code>headerFilterStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> Reference to a instance of <code>org.apache.camel.spi.HeaderFilterStrategy</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. It will be used to apply the custom headerFilterStrategy on the new create HttpJettyEndpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>urlRewrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> Refers to a custom <code>org.apache.camel.component.http.UrlRewrite</code> which allows you to rewrite urls when you bridge/proxy endpoints. See more details at <a shape="rect" href="urlrewrite.html" title="UrlRewrite">UrlRewrite</
 a> and <a shape="rect" href="how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html" title="How to use Camel as a HTTP proxy between a client and server">How to use Camel as a HTTP proxy between a client and server</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>responseBufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12:</strong> To use a custom buffer size on the <code>javax.servlet.ServletResponse</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> The http proxy Host url which will be used by Jetty client. </p></td></tr><tr><td colspan="1" rowspan="1" class="conf
 luenceTd"><p> <code>proxyPort</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> The http proxy port which will be used by Jetty client. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sendServerVersion</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.13:</strong> if the option is true, jetty will send the server header with the jetty version information to the client which sends the request. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>SendDateHeader</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 the option is true, jett
 y server will send the date header to the client which sends the request. </p></td></tr></tbody></table>
 </div><h3 id="BookInOnePage-MessageHeaders.9">Message Headers</h3><p>Camel uses the same message headers as the <a shape="rect" href="http.html">HTTP</a> component.<br clear="none"> From Camel 2.2, it also uses (Exchange.HTTP_CHUNKED,CamelHttpChunked) header to turn on or turn off the chuched encoding on the camel-jetty consumer.</p><p>Camel also populates <strong>all</strong> request.parameter and request.headers. For example, given a client request with the URL, <code><a shape="rect" class="external-link" href="http://myserver/myserver?orderid=123" rel="nofollow">http://myserver/myserver?orderid=123</a></code>, the exchange will contain a header named <code>orderid</code> with the value 123.</p><p>Starting with Camel 2.2.0, you can get the request.parameter from the message header not only from Get Method, but also other HTTP method.</p><h3 id="BookInOnePage-Usage.4">Usage</h3><p>The Jetty component supports both consumer and producer endpoints. Another option for producing to oth
 er HTTP endpoints, is to use the <a shape="rect" href="http.html">HTTP Component</a></p><h3 id="BookInOnePage-ComponentOptions">Component Options</h3><p>The <code>JettyHttpComponent</code> provides the following options:</p><div class="confluenceTableSmall">

[... 12 lines stripped ...]


Mime
View raw message