Author: buildbot
Date: Mon May 7 08:25:41 2012
New Revision: 816280
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/book-pattern-appendix.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/routing-slip.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 Mon May 7 08:25:41
2012
@@ -17271,7 +17271,7 @@ from(<span class="code-quote">"seda:quot
<h3><a shape="rect" name="BookInOnePage-Options"></a>Options</h3>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>uriDelimiter</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>,</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Delimiter used if the <a shape="rect"
href="expression.html" title="Expression">Expression</a> returned multiple
endpoints. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>ignoreInvalidEndpoints</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If an endpoint uri could not be resolved, should it be
ignored. Otherwise Camel will thrown an exception stating the endpoint uri is
not valid. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>uriDelimiter</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>,</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Delimiter used if the <a shape="rect"
href="expression.html" title="Expression">Expression</a> returned multiple
endpoints. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>ignoreInvalidEndpoints</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If an endpoint uri could not be resolved, should it be
ignored. Otherwise Camel will throw an exception stating the endpoint uri is
not valid. </td></tr></tbody></table>
</div>
</div>
@@ -17319,7 +17319,7 @@ from(<span class="code-quote">"activemq:
<h3><a shape="rect" name="BookInOnePage-Ignoreinvalidendpoints"></a>Ignore
invalid endpoints</h3>
<p><b>Available as of Camel 2.3</b></p>
-<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports <tt>ignoreInvalidEndpoints</tt> which the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> also
supports. You can use it to skip endpoints which is invalid.</p>
+<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports <tt>ignoreInvalidEndpoints</tt> which the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> also
supports. You can use it to skip endpoints which are invalid.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
@@ -17338,12 +17338,12 @@ from(<span class="code-quote">"activemq:
</pre>
</div></div>
-<p>Then lets say the <tt>myHeader</tt> contains the following two endpoints
<tt>direct:foo,xxx:bar</tt>. The first endpoint is valid and works. However the
2nd is invalid and will just be ignored. Camel logs at INFO level about, so you
can see why the endpoint was invalid.</p>
+<p>Then lets say the <tt>myHeader</tt> contains the following two endpoints
<tt>direct:foo,xxx:bar</tt>. The first endpoint is valid and works. However the
2nd is invalid and will just be ignored. Camel logs at INFO level, so you can
see why the endpoint was invalid.</p>
<h3><a shape="rect" name="BookInOnePage-Expressionsupporting"></a>Expression
supporting</h3>
<p><b>Available as of Camel 2.4</b></p>
-<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports to take the expression parameter as the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> does. You
can tell the camel the expression that you want to use to get the routing
slip.</p>
+<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports to take the expression parameter as the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> does. You
can tell Camel the expression that you want to use to get the routing slip.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
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 Mon May 7
08:25:41 2012
@@ -3099,7 +3099,7 @@ from(<span class="code-quote">"seda:quot
<h3><a shape="rect" name="BookPatternAppendix-Options"></a>Options</h3>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>uriDelimiter</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>,</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Delimiter used if the <a shape="rect"
href="expression.html" title="Expression">Expression</a> returned multiple
endpoints. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>ignoreInvalidEndpoints</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If an endpoint uri could not be resolved, should it be
ignored. Otherwise Camel will thrown an exception stating the endpoint uri is
not valid. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>uriDelimiter</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>,</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Delimiter used if the <a shape="rect"
href="expression.html" title="Expression">Expression</a> returned multiple
endpoints. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>ignoreInvalidEndpoints</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If an endpoint uri could not be resolved, should it be
ignored. Otherwise Camel will throw an exception stating the endpoint uri is
not valid. </td></tr></tbody></table>
</div>
</div>
@@ -3147,7 +3147,7 @@ from(<span class="code-quote">"activemq:
<h3><a shape="rect"
name="BookPatternAppendix-Ignoreinvalidendpoints"></a>Ignore invalid
endpoints</h3>
<p><b>Available as of Camel 2.3</b></p>
-<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports <tt>ignoreInvalidEndpoints</tt> which the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> also
supports. You can use it to skip endpoints which is invalid.</p>
+<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports <tt>ignoreInvalidEndpoints</tt> which the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> also
supports. You can use it to skip endpoints which are invalid.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
@@ -3166,12 +3166,12 @@ from(<span class="code-quote">"activemq:
</pre>
</div></div>
-<p>Then lets say the <tt>myHeader</tt> contains the following two endpoints
<tt>direct:foo,xxx:bar</tt>. The first endpoint is valid and works. However the
2nd is invalid and will just be ignored. Camel logs at INFO level about, so you
can see why the endpoint was invalid.</p>
+<p>Then lets say the <tt>myHeader</tt> contains the following two endpoints
<tt>direct:foo,xxx:bar</tt>. The first endpoint is valid and works. However the
2nd is invalid and will just be ignored. Camel logs at INFO level, so you can
see why the endpoint was invalid.</p>
<h3><a shape="rect"
name="BookPatternAppendix-Expressionsupporting"></a>Expression supporting</h3>
<p><b>Available as of Camel 2.4</b></p>
-<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports to take the expression parameter as the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> does. You
can tell the camel the expression that you want to use to get the routing
slip.</p>
+<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports to take the expression parameter as the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> does. You
can tell Camel the expression that you want to use to get the routing slip.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/routing-slip.html
==============================================================================
--- websites/production/camel/content/routing-slip.html (original)
+++ websites/production/camel/content/routing-slip.html Mon May 7 08:25:41 2012
@@ -84,7 +84,7 @@
<h3><a shape="rect" name="RoutingSlip-Options"></a>Options</h3>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>uriDelimiter</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>,</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Delimiter used if the <a shape="rect"
href="expression.html" title="Expression">Expression</a> returned multiple
endpoints. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>ignoreInvalidEndpoints</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If an endpoint uri could not be resolved, should it be
ignored. Otherwise Camel will thrown an exception stating the endpoint uri is
not valid. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>uriDelimiter</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>,</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Delimiter used if the <a shape="rect"
href="expression.html" title="Expression">Expression</a> returned multiple
endpoints. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>ignoreInvalidEndpoints</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If an endpoint uri could not be resolved, should it be
ignored. Otherwise Camel will throw an exception stating the endpoint uri is
not valid. </td></tr></tbody></table>
</div>
</div>
@@ -132,7 +132,7 @@ from(<span class="code-quote">"activemq:
<h3><a shape="rect" name="RoutingSlip-Ignoreinvalidendpoints"></a>Ignore
invalid endpoints</h3>
<p><b>Available as of Camel 2.3</b></p>
-<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports <tt>ignoreInvalidEndpoints</tt> which the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> also
supports. You can use it to skip endpoints which is invalid.</p>
+<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports <tt>ignoreInvalidEndpoints</tt> which the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> also
supports. You can use it to skip endpoints which are invalid.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
@@ -151,12 +151,12 @@ from(<span class="code-quote">"activemq:
</pre>
</div></div>
-<p>Then lets say the <tt>myHeader</tt> contains the following two endpoints
<tt>direct:foo,xxx:bar</tt>. The first endpoint is valid and works. However the
2nd is invalid and will just be ignored. Camel logs at INFO level about, so you
can see why the endpoint was invalid.</p>
+<p>Then lets say the <tt>myHeader</tt> contains the following two endpoints
<tt>direct:foo,xxx:bar</tt>. The first endpoint is valid and works. However the
2nd is invalid and will just be ignored. Camel logs at INFO level, so you can
see why the endpoint was invalid.</p>
<h3><a shape="rect" name="RoutingSlip-Expressionsupporting"></a>Expression
supporting</h3>
<p><b>Available as of Camel 2.4</b></p>
-<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports to take the expression parameter as the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> does. You
can tell the camel the expression that you want to use to get the routing
slip.</p>
+<p>The <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing
Slip</a> now supports to take the expression parameter as the <a shape="rect"
href="recipient-list.html" title="Recipient List">Recipient List</a> does. You
can tell Camel the expression that you want to use to get the routing slip.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
