Author: buildbot
Date: Fri Apr 6 12:21:32 2012
New Revision: 811687
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-component-appendix.html
websites/production/camel/content/book-cookbook.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/mock.html
Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Fri Apr 6
12:21:32 2012
@@ -10853,7 +10853,7 @@ You can get the IoSession from the messa
<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Mock endpoints keep received Exchanges in memory
indefinitely</b><br clear="none">Remember that Mock is designed for testing.
When you add Mock endpoints to a route, each <a shape="rect"
href="exchange.html" title="Exchange">Exchange</a> sent to the endpoint will be
stored (to allow for later validation) in memory until explicitly reset or the
JVM is restarted. If you are sending high volume and/or large messages, this
may cause excessive memory use. If your goal is to test deployable routes
inline, consider using <a shape="rect" href="notifybuilder.html"
title="NotifyBuilder">NotifyBuilder</a> or <a shape="rect"
href="advicewith.html"
title="AdviceWith">AdviceWith</a> in your tests instead of adding Mock
endpoints to routes directly.
-<p>From Camel 2.10 onwards there is two new options <tt>retainFirst</tt>, and
<tt>retainLast</tt> that can be used to limit the number of messages the Mock
endpoints keep in memory.</p></td></tr></table></div>
+<p>From Camel 2.10 onwards there are two new options <tt>retainFirst</tt>, and
<tt>retainLast</tt> that can be used to limit the number of messages the Mock
endpoints keep in memory.</p></td></tr></table></div>
<h3><a shape="rect" name="BookComponentAppendix-URIformat"></a>URI format</h3>
@@ -11230,7 +11230,7 @@ The solution is to create a new XML file
<p>The <a shape="rect" href="mock.html" title="Mock">Mock</a> endpoints will
by default keep a copy of every <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a> that it received. So if you test with a lot of
messages, then it will consume memory.<br clear="none">
From Camel 2.10 onwards we have introduced two options <tt>retainFirst</tt>
and <tt>retainLast</tt> that can be used to specify to only keep N'th of the
first and/or last <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s.</p>
-<p>For example in the code below, we only want to retrain a copy of the first
5 and last 5 <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s the mock receives.</p>
+<p>For example in the code below, we only want to retain a copy of the first 5
and last 5 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s
the mock receives.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
MockEndpoint mock = getMockEndpoint(<span
class="code-quote">"mock:data"</span>);
@@ -11244,8 +11244,8 @@ From Camel 2.10 onwards we have introduc
</pre>
</div></div>
-<p>Using this have some limitations. As the <tt>getExchanges()</tt> and
<tt>getReceivedExchanges()</tt> method on the <tt>MockEndpoint</tt>, will only
return the retained copies of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s. So in the example above, the list will contain
10 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s; the
first five, and the last five.<br clear="none">
-Using the <tt>retainFirst</tt> and <tt>retainLast</tt> options have
<b>limitations</b> on which expectation methods you can use. For example the
expectedXXX methods that works on message bodies, headers, etc. will only
operate on the retrained messages. In the example above they can only test the
expectations on the 10 retained messages.</p>
+<p>Using this has some limitations. The <tt>getExchanges()</tt> and
<tt>getReceivedExchanges()</tt> methods on the <tt>MockEndpoint</tt> will
return only the retained copies of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s. So in the example above, the list will contain
10 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s; the
first five, and the last five.<br clear="none">
+The <tt>retainFirst</tt> and <tt>retainLast</tt> options also have limitations
on which expectation methods you can use. For example the expectedXXX methods
that work on message bodies, headers, etc. will only operate on the retained
messages. In the example above they can test only the expectations on the 10
retained messages.</p>
<h3><a shape="rect"
name="BookComponentAppendix-Testingwitharrivaltimes"></a>Testing with arrival
times</h3>
Modified: websites/production/camel/content/book-cookbook.html
==============================================================================
--- websites/production/camel/content/book-cookbook.html (original)
+++ websites/production/camel/content/book-cookbook.html Fri Apr 6 12:21:32
2012
@@ -1105,7 +1105,7 @@ See the <a shape="rect" href="bean-integ
<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Mock endpoints keep received Exchanges in memory
indefinitely</b><br clear="none">Remember that Mock is designed for testing.
When you add Mock endpoints to a route, each <a shape="rect"
href="exchange.html" title="Exchange">Exchange</a> sent to the endpoint will be
stored (to allow for later validation) in memory until explicitly reset or the
JVM is restarted. If you are sending high volume and/or large messages, this
may cause excessive memory use. If your goal is to test deployable routes
inline, consider using <a shape="rect" href="notifybuilder.html"
title="NotifyBuilder">NotifyBuilder</a> or <a shape="rect"
href="advicewith.html"
title="AdviceWith">AdviceWith</a> in your tests instead of adding Mock
endpoints to routes directly.
-<p>From Camel 2.10 onwards there is two new options <tt>retainFirst</tt>, and
<tt>retainLast</tt> that can be used to limit the number of messages the Mock
endpoints keep in memory.</p></td></tr></table></div>
+<p>From Camel 2.10 onwards there are two new options <tt>retainFirst</tt>, and
<tt>retainLast</tt> that can be used to limit the number of messages the Mock
endpoints keep in memory.</p></td></tr></table></div>
<h3><a shape="rect" name="Bookcookbook-URIformat"></a>URI format</h3>
@@ -1482,7 +1482,7 @@ The solution is to create a new XML file
<p>The <a shape="rect" href="mock.html" title="Mock">Mock</a> endpoints will
by default keep a copy of every <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a> that it received. So if you test with a lot of
messages, then it will consume memory.<br clear="none">
From Camel 2.10 onwards we have introduced two options <tt>retainFirst</tt>
and <tt>retainLast</tt> that can be used to specify to only keep N'th of the
first and/or last <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s.</p>
-<p>For example in the code below, we only want to retrain a copy of the first
5 and last 5 <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s the mock receives.</p>
+<p>For example in the code below, we only want to retain a copy of the first 5
and last 5 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s
the mock receives.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
MockEndpoint mock = getMockEndpoint(<span
class="code-quote">"mock:data"</span>);
@@ -1496,8 +1496,8 @@ From Camel 2.10 onwards we have introduc
</pre>
</div></div>
-<p>Using this have some limitations. As the <tt>getExchanges()</tt> and
<tt>getReceivedExchanges()</tt> method on the <tt>MockEndpoint</tt>, will only
return the retained copies of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s. So in the example above, the list will contain
10 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s; the
first five, and the last five.<br clear="none">
-Using the <tt>retainFirst</tt> and <tt>retainLast</tt> options have
<b>limitations</b> on which expectation methods you can use. For example the
expectedXXX methods that works on message bodies, headers, etc. will only
operate on the retrained messages. In the example above they can only test the
expectations on the 10 retained messages.</p>
+<p>Using this has some limitations. The <tt>getExchanges()</tt> and
<tt>getReceivedExchanges()</tt> methods on the <tt>MockEndpoint</tt> will
return only the retained copies of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s. So in the example above, the list will contain
10 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s; the
first five, and the last five.<br clear="none">
+The <tt>retainFirst</tt> and <tt>retainLast</tt> options also have limitations
on which expectation methods you can use. For example the expectedXXX methods
that work on message bodies, headers, etc. will only operate on the retained
messages. In the example above they can test only the expectations on the 10
retained messages.</p>
<h3><a shape="rect" name="Bookcookbook-Testingwitharrivaltimes"></a>Testing
with arrival times</h3>
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 Fri Apr 6 12:21:32
2012
@@ -2232,7 +2232,7 @@ See the <a shape="rect" href="bean-integ
<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Mock endpoints keep received Exchanges in memory
indefinitely</b><br clear="none">Remember that Mock is designed for testing.
When you add Mock endpoints to a route, each <a shape="rect"
href="exchange.html" title="Exchange">Exchange</a> sent to the endpoint will be
stored (to allow for later validation) in memory until explicitly reset or the
JVM is restarted. If you are sending high volume and/or large messages, this
may cause excessive memory use. If your goal is to test deployable routes
inline, consider using <a shape="rect" href="notifybuilder.html"
title="NotifyBuilder">NotifyBuilder</a> or <a shape="rect"
href="advicewith.html"
title="AdviceWith">AdviceWith</a> in your tests instead of adding Mock
endpoints to routes directly.
-<p>From Camel 2.10 onwards there is two new options <tt>retainFirst</tt>, and
<tt>retainLast</tt> that can be used to limit the number of messages the Mock
endpoints keep in memory.</p></td></tr></table></div>
+<p>From Camel 2.10 onwards there are two new options <tt>retainFirst</tt>, and
<tt>retainLast</tt> that can be used to limit the number of messages the Mock
endpoints keep in memory.</p></td></tr></table></div>
<h3><a shape="rect" name="BookInOnePage-URIformat"></a>URI format</h3>
@@ -2609,7 +2609,7 @@ The solution is to create a new XML file
<p>The <a shape="rect" href="mock.html" title="Mock">Mock</a> endpoints will
by default keep a copy of every <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a> that it received. So if you test with a lot of
messages, then it will consume memory.<br clear="none">
From Camel 2.10 onwards we have introduced two options <tt>retainFirst</tt>
and <tt>retainLast</tt> that can be used to specify to only keep N'th of the
first and/or last <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s.</p>
-<p>For example in the code below, we only want to retrain a copy of the first
5 and last 5 <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s the mock receives.</p>
+<p>For example in the code below, we only want to retain a copy of the first 5
and last 5 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s
the mock receives.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
MockEndpoint mock = getMockEndpoint(<span
class="code-quote">"mock:data"</span>);
@@ -2623,8 +2623,8 @@ From Camel 2.10 onwards we have introduc
</pre>
</div></div>
-<p>Using this have some limitations. As the <tt>getExchanges()</tt> and
<tt>getReceivedExchanges()</tt> method on the <tt>MockEndpoint</tt>, will only
return the retained copies of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s. So in the example above, the list will contain
10 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s; the
first five, and the last five.<br clear="none">
-Using the <tt>retainFirst</tt> and <tt>retainLast</tt> options have
<b>limitations</b> on which expectation methods you can use. For example the
expectedXXX methods that works on message bodies, headers, etc. will only
operate on the retrained messages. In the example above they can only test the
expectations on the 10 retained messages.</p>
+<p>Using this has some limitations. The <tt>getExchanges()</tt> and
<tt>getReceivedExchanges()</tt> methods on the <tt>MockEndpoint</tt> will
return only the retained copies of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s. So in the example above, the list will contain
10 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s; the
first five, and the last five.<br clear="none">
+The <tt>retainFirst</tt> and <tt>retainLast</tt> options also have limitations
on which expectation methods you can use. For example the expectedXXX methods
that work on message bodies, headers, etc. will only operate on the retained
messages. In the example above they can test only the expectations on the 10
retained messages.</p>
<h3><a shape="rect" name="BookInOnePage-Testingwitharrivaltimes"></a>Testing
with arrival times</h3>
@@ -31014,7 +31014,7 @@ You can get the IoSession from the messa
<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Mock endpoints keep received Exchanges in memory
indefinitely</b><br clear="none">Remember that Mock is designed for testing.
When you add Mock endpoints to a route, each <a shape="rect"
href="exchange.html" title="Exchange">Exchange</a> sent to the endpoint will be
stored (to allow for later validation) in memory until explicitly reset or the
JVM is restarted. If you are sending high volume and/or large messages, this
may cause excessive memory use. If your goal is to test deployable routes
inline, consider using <a shape="rect" href="notifybuilder.html"
title="NotifyBuilder">NotifyBuilder</a> or <a shape="rect"
href="advicewith.html"
title="AdviceWith">AdviceWith</a> in your tests instead of adding Mock
endpoints to routes directly.
-<p>From Camel 2.10 onwards there is two new options <tt>retainFirst</tt>, and
<tt>retainLast</tt> that can be used to limit the number of messages the Mock
endpoints keep in memory.</p></td></tr></table></div>
+<p>From Camel 2.10 onwards there are two new options <tt>retainFirst</tt>, and
<tt>retainLast</tt> that can be used to limit the number of messages the Mock
endpoints keep in memory.</p></td></tr></table></div>
<h3><a shape="rect" name="BookInOnePage-URIformat"></a>URI format</h3>
@@ -31391,7 +31391,7 @@ The solution is to create a new XML file
<p>The <a shape="rect" href="mock.html" title="Mock">Mock</a> endpoints will
by default keep a copy of every <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a> that it received. So if you test with a lot of
messages, then it will consume memory.<br clear="none">
From Camel 2.10 onwards we have introduced two options <tt>retainFirst</tt>
and <tt>retainLast</tt> that can be used to specify to only keep N'th of the
first and/or last <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s.</p>
-<p>For example in the code below, we only want to retrain a copy of the first
5 and last 5 <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s the mock receives.</p>
+<p>For example in the code below, we only want to retain a copy of the first 5
and last 5 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s
the mock receives.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
MockEndpoint mock = getMockEndpoint(<span
class="code-quote">"mock:data"</span>);
@@ -31405,8 +31405,8 @@ From Camel 2.10 onwards we have introduc
</pre>
</div></div>
-<p>Using this have some limitations. As the <tt>getExchanges()</tt> and
<tt>getReceivedExchanges()</tt> method on the <tt>MockEndpoint</tt>, will only
return the retained copies of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s. So in the example above, the list will contain
10 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s; the
first five, and the last five.<br clear="none">
-Using the <tt>retainFirst</tt> and <tt>retainLast</tt> options have
<b>limitations</b> on which expectation methods you can use. For example the
expectedXXX methods that works on message bodies, headers, etc. will only
operate on the retrained messages. In the example above they can only test the
expectations on the 10 retained messages.</p>
+<p>Using this has some limitations. The <tt>getExchanges()</tt> and
<tt>getReceivedExchanges()</tt> methods on the <tt>MockEndpoint</tt> will
return only the retained copies of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s. So in the example above, the list will contain
10 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s; the
first five, and the last five.<br clear="none">
+The <tt>retainFirst</tt> and <tt>retainLast</tt> options also have limitations
on which expectation methods you can use. For example the expectedXXX methods
that work on message bodies, headers, etc. will only operate on the retained
messages. In the example above they can test only the expectations on the 10
retained messages.</p>
<h3><a shape="rect" name="BookInOnePage-Testingwitharrivaltimes"></a>Testing
with arrival times</h3>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/mock.html
==============================================================================
--- websites/production/camel/content/mock.html (original)
+++ websites/production/camel/content/mock.html Fri Apr 6 12:21:32 2012
@@ -89,7 +89,7 @@
<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Mock endpoints keep received Exchanges in memory
indefinitely</b><br clear="none">Remember that Mock is designed for testing.
When you add Mock endpoints to a route, each <a shape="rect"
href="exchange.html" title="Exchange">Exchange</a> sent to the endpoint will be
stored (to allow for later validation) in memory until explicitly reset or the
JVM is restarted. If you are sending high volume and/or large messages, this
may cause excessive memory use. If your goal is to test deployable routes
inline, consider using <a shape="rect" href="notifybuilder.html"
title="NotifyBuilder">NotifyBuilder</a> or <a shape="rect"
href="advicewith.html"
title="AdviceWith">AdviceWith</a> in your tests instead of adding Mock
endpoints to routes directly.
-<p>From Camel 2.10 onwards there is two new options <tt>retainFirst</tt>, and
<tt>retainLast</tt> that can be used to limit the number of messages the Mock
endpoints keep in memory.</p></td></tr></table></div>
+<p>From Camel 2.10 onwards there are two new options <tt>retainFirst</tt>, and
<tt>retainLast</tt> that can be used to limit the number of messages the Mock
endpoints keep in memory.</p></td></tr></table></div>
<h3><a shape="rect" name="Mock-URIformat"></a>URI format</h3>
@@ -466,7 +466,7 @@ The solution is to create a new XML file
<p>The <a shape="rect" href="mock.html" title="Mock">Mock</a> endpoints will
by default keep a copy of every <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a> that it received. So if you test with a lot of
messages, then it will consume memory.<br clear="none">
From Camel 2.10 onwards we have introduced two options <tt>retainFirst</tt>
and <tt>retainLast</tt> that can be used to specify to only keep N'th of the
first and/or last <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s.</p>
-<p>For example in the code below, we only want to retrain a copy of the first
5 and last 5 <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s the mock receives.</p>
+<p>For example in the code below, we only want to retain a copy of the first 5
and last 5 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s
the mock receives.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
MockEndpoint mock = getMockEndpoint(<span
class="code-quote">"mock:data"</span>);
@@ -480,8 +480,8 @@ From Camel 2.10 onwards we have introduc
</pre>
</div></div>
-<p>Using this have some limitations. As the <tt>getExchanges()</tt> and
<tt>getReceivedExchanges()</tt> method on the <tt>MockEndpoint</tt>, will only
return the retained copies of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s. So in the example above, the list will contain
10 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s; the
first five, and the last five.<br clear="none">
-Using the <tt>retainFirst</tt> and <tt>retainLast</tt> options have
<b>limitations</b> on which expectation methods you can use. For example the
expectedXXX methods that works on message bodies, headers, etc. will only
operate on the retrained messages. In the example above they can only test the
expectations on the 10 retained messages.</p>
+<p>Using this has some limitations. The <tt>getExchanges()</tt> and
<tt>getReceivedExchanges()</tt> methods on the <tt>MockEndpoint</tt> will
return only the retained copies of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>s. So in the example above, the list will contain
10 <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s; the
first five, and the last five.<br clear="none">
+The <tt>retainFirst</tt> and <tt>retainLast</tt> options also have limitations
on which expectation methods you can use. For example the expectedXXX methods
that work on message bodies, headers, etc. will only operate on the retained
messages. In the example above they can test only the expectations on the 10
retained messages.</p>
<h3><a shape="rect" name="Mock-Testingwitharrivaltimes"></a>Testing with
arrival times</h3>
![https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif"){kind=link}