Author: buildbot
Date: Fri Apr 6 16:20:36 2012
New Revision: 811709
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-component-appendix.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-2100-release.html
websites/production/camel/content/mybatis.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
16:20:36 2012
@@ -11408,12 +11408,12 @@ mybatis:statementName[?options]
<p>You can append query options to the URI in the following format,
<tt>?option=value&option=value&...</tt></p>
-<p>This component will by default load the MyBatis SqlMapConfig file from the
root of the classpath and expected named as <tt>SqlMapConfig.xml</tt>.<br
clear="none">
-If the file is located in another location, you would have to configure the
<tt>configurationUri</tt> option on the <tt>MyBatisComponent</tt> component.</p>
+<p>This component will by default load the MyBatis SqlMapConfig file from the
root of the classpath with the expected name of <tt>SqlMapConfig.xml</tt>.<br
clear="none">
+If the file is located in another location, you will need to configure the
<tt>configurationUri</tt> option on the <tt>MyBatisComponent</tt> component.</p>
<h3><a shape="rect" name="BookComponentAppendix-Options"></a>Options</h3>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>consumer.onConsume</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Statements to run after consuming. Can be
used, for example, to update rows after they have been consumed and processed
in Camel. See sample later. Multiple statements can be separated with comma.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.useIterator</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluence
Td"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If
<tt>true</tt> each row returned when polling will be processed individually. If
<tt>false</tt> the entire <tt>List</tt> of data is set as the IN body.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.routeEmptyResultSet</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets whether empty result set should be routed or not. By
default, empty result sets are not routed. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>statementType</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>StatementType</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Mandatory to specify for producer to control
which kind of operation to
invoke. The enum values are: <tt>SelectOne</tt>, <tt>SelectList</tt>,
<tt>Insert</tt>, <tt>InsertList</tt>, <tt>Update</tt>, <tt>Delete</tt>.
<b>Notice:</b> <tt>InsertList</tt> is available as of Camel 2.10.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>maxMessagesPerPoll</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>int</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> An integer to define a maximum messages to gather per
poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to
avoid when starting up the server that there are thousands of files. Set a
value of 0 or negative to disabled it. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>consumer.onConsume</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Statements to run after consuming. Can be
used, for example, to update rows after they have been consumed and processed
in Camel. See sample later. Multiple statements can be separated with commas.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.useIterator</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenc
eTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If
<tt>true</tt> each row returned when polling will be processed individually. If
<tt>false</tt> the entire <tt>List</tt> of data is set as the IN body.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.routeEmptyResultSet</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets whether empty result sets should be routed.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>statementType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>StatementType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Mandatory
to specify for the producer to control which kind of operation to invoke. The
enum values are: <tt>SelectOne</tt>
, <tt>SelectList</tt>, <tt>Insert</tt>, <tt>InsertList</tt>, <tt>Update</tt>,
<tt>Delete</tt>. <b>Notice:</b> <tt>InsertList</tt> is available as of Camel
2.10. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>maxMessagesPerPoll</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>int</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> An integer to define the maximum messages to gather per
poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to
avoid when starting up the server that there are thousands of files. Set a
value of 0 or negative to disable it. </td></tr></tbody></table>
</div>
</div>
@@ -11425,7 +11425,7 @@ If the file is located in another locati
</div>
<h3><a shape="rect" name="BookComponentAppendix-MessageBody"></a>Message
Body</h3>
-<p>The response from MyBatis will only be set as body if it's a
<tt>SELECT</tt> statement. That means, for example, for <tt>INSERT</tt>
statements Camel will not replace the body. This allows you to continue routing
and keep the original body. The response from MyBatis is always stored in the
header with the key <tt>CamelMyBatisResult</tt>.</p>
+<p>The response from MyBatis will only be set as the body if it's a
<tt>SELECT</tt> statement. That means, for example, for <tt>INSERT</tt>
statements Camel will not replace the body. This allows you to continue routing
and keep the original body. The response from MyBatis is always stored in the
header with the key <tt>CamelMyBatisResult</tt>.</p>
<h3><a shape="rect" name="BookComponentAppendix-Samples"></a>Samples</h3>
@@ -11459,7 +11459,7 @@ from(<span class="code-quote">"activemq:
</div></div>
<h3><a shape="rect"
name="BookComponentAppendix-UsingStatementTypeforbettercontrolofMyBatis"></a>Using
StatementType for better control of MyBatis</h3>
-<p>When routing to an MyBatis endpoint you want more fine grained control so
you can control whether the SQL statement to be executed is a <tt>SELEECT</tt>,
<tt>UPDATE</tt>, <tt>DELETE</tt> or <tt>INSERT</tt> etc. So for instance if we
want to route to an MyBatis endpoint in which the IN body contains parameters
to a <tt>SELECT</tt> statement we can do:</p>
+<p>When routing to an MyBatis endpoint you will want more fine grained control
so you can control whether the SQL statement to be executed is a
<tt>SELECT</tt>, <tt>UPDATE</tt>, <tt>DELETE</tt> or <tt>INSERT</tt> etc. So
for instance if we want to route to an MyBatis endpoint in which the IN body
contains parameters to a <tt>SELECT</tt> statement we can do:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">from(<span class="code-quote">"direct:start"</span>)
.to(<span
class="code-quote">"mybatis:selectAccountById?statementType=SelectOne"</span>)
@@ -11477,7 +11477,7 @@ from(<span class="code-quote">"activemq:
</pre>
</div></div>
-<p>And the same for <tt>UPDATE</tt>, where we can send an <tt>Account</tt>
object as IN body to MyBatis:</p>
+<p>And the same for <tt>UPDATE</tt>, where we can send an <tt>Account</tt>
object as the IN body to MyBatis:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">from(<span class="code-quote">"direct:start"</span>)
.to(<span
class="code-quote">"mybatis:updateAccount?statementType=Update"</span>)
@@ -11537,7 +11537,7 @@ from(<span class="code-quote">"timer:<sp
</div></div>
<h4><a shape="rect" name="BookComponentAppendix-UsingonConsume"></a>Using
onConsume</h4>
-<p>This component supports executing statements <b>after</b> data have been
consumed and processed by Camel. This allows you to do post updates in the
database. Notice all statements must be <tt>UPDATE</tt> statements. Camel
supports executing multiple statements whose name should be separated by
comma.</p>
+<p>This component supports executing statements <b>after</b> data have been
consumed and processed by Camel. This allows you to do post updates in the
database. Notice all statements must be <tt>UPDATE</tt> statements. Camel
supports executing multiple statements whose names should be separated by
commas.</p>
<p>The route below illustrates we execute the <b>consumeAccount</b> statement
data is processed. This allows us to change the status of the row in the
database to processed, so we avoid consuming it twice or more.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
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 16:20:36
2012
@@ -31569,12 +31569,12 @@ mybatis:statementName[?options]
<p>You can append query options to the URI in the following format,
<tt>?option=value&option=value&...</tt></p>
-<p>This component will by default load the MyBatis SqlMapConfig file from the
root of the classpath and expected named as <tt>SqlMapConfig.xml</tt>.<br
clear="none">
-If the file is located in another location, you would have to configure the
<tt>configurationUri</tt> option on the <tt>MyBatisComponent</tt> component.</p>
+<p>This component will by default load the MyBatis SqlMapConfig file from the
root of the classpath with the expected name of <tt>SqlMapConfig.xml</tt>.<br
clear="none">
+If the file is located in another location, you will need to configure the
<tt>configurationUri</tt> option on the <tt>MyBatisComponent</tt> component.</p>
<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"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>consumer.onConsume</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Statements to run after consuming. Can be
used, for example, to update rows after they have been consumed and processed
in Camel. See sample later. Multiple statements can be separated with comma.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.useIterator</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluence
Td"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If
<tt>true</tt> each row returned when polling will be processed individually. If
<tt>false</tt> the entire <tt>List</tt> of data is set as the IN body.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.routeEmptyResultSet</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets whether empty result set should be routed or not. By
default, empty result sets are not routed. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>statementType</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>StatementType</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Mandatory to specify for producer to control
which kind of operation to
invoke. The enum values are: <tt>SelectOne</tt>, <tt>SelectList</tt>,
<tt>Insert</tt>, <tt>InsertList</tt>, <tt>Update</tt>, <tt>Delete</tt>.
<b>Notice:</b> <tt>InsertList</tt> is available as of Camel 2.10.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>maxMessagesPerPoll</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>int</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> An integer to define a maximum messages to gather per
poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to
avoid when starting up the server that there are thousands of files. Set a
value of 0 or negative to disabled it. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>consumer.onConsume</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Statements to run after consuming. Can be
used, for example, to update rows after they have been consumed and processed
in Camel. See sample later. Multiple statements can be separated with commas.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.useIterator</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenc
eTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If
<tt>true</tt> each row returned when polling will be processed individually. If
<tt>false</tt> the entire <tt>List</tt> of data is set as the IN body.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.routeEmptyResultSet</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets whether empty result sets should be routed.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>statementType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>StatementType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Mandatory
to specify for the producer to control which kind of operation to invoke. The
enum values are: <tt>SelectOne</tt>
, <tt>SelectList</tt>, <tt>Insert</tt>, <tt>InsertList</tt>, <tt>Update</tt>,
<tt>Delete</tt>. <b>Notice:</b> <tt>InsertList</tt> is available as of Camel
2.10. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>maxMessagesPerPoll</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>int</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> An integer to define the maximum messages to gather per
poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to
avoid when starting up the server that there are thousands of files. Set a
value of 0 or negative to disable it. </td></tr></tbody></table>
</div>
</div>
@@ -31586,7 +31586,7 @@ If the file is located in another locati
</div>
<h3><a shape="rect" name="BookInOnePage-MessageBody"></a>Message Body</h3>
-<p>The response from MyBatis will only be set as body if it's a
<tt>SELECT</tt> statement. That means, for example, for <tt>INSERT</tt>
statements Camel will not replace the body. This allows you to continue routing
and keep the original body. The response from MyBatis is always stored in the
header with the key <tt>CamelMyBatisResult</tt>.</p>
+<p>The response from MyBatis will only be set as the body if it's a
<tt>SELECT</tt> statement. That means, for example, for <tt>INSERT</tt>
statements Camel will not replace the body. This allows you to continue routing
and keep the original body. The response from MyBatis is always stored in the
header with the key <tt>CamelMyBatisResult</tt>.</p>
<h3><a shape="rect" name="BookInOnePage-Samples"></a>Samples</h3>
@@ -31620,7 +31620,7 @@ from(<span class="code-quote">"activemq:
</div></div>
<h3><a shape="rect"
name="BookInOnePage-UsingStatementTypeforbettercontrolofMyBatis"></a>Using
StatementType for better control of MyBatis</h3>
-<p>When routing to an MyBatis endpoint you want more fine grained control so
you can control whether the SQL statement to be executed is a <tt>SELEECT</tt>,
<tt>UPDATE</tt>, <tt>DELETE</tt> or <tt>INSERT</tt> etc. So for instance if we
want to route to an MyBatis endpoint in which the IN body contains parameters
to a <tt>SELECT</tt> statement we can do:</p>
+<p>When routing to an MyBatis endpoint you will want more fine grained control
so you can control whether the SQL statement to be executed is a
<tt>SELECT</tt>, <tt>UPDATE</tt>, <tt>DELETE</tt> or <tt>INSERT</tt> etc. So
for instance if we want to route to an MyBatis endpoint in which the IN body
contains parameters to a <tt>SELECT</tt> statement we can do:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">from(<span class="code-quote">"direct:start"</span>)
.to(<span
class="code-quote">"mybatis:selectAccountById?statementType=SelectOne"</span>)
@@ -31638,7 +31638,7 @@ from(<span class="code-quote">"activemq:
</pre>
</div></div>
-<p>And the same for <tt>UPDATE</tt>, where we can send an <tt>Account</tt>
object as IN body to MyBatis:</p>
+<p>And the same for <tt>UPDATE</tt>, where we can send an <tt>Account</tt>
object as the IN body to MyBatis:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">from(<span class="code-quote">"direct:start"</span>)
.to(<span
class="code-quote">"mybatis:updateAccount?statementType=Update"</span>)
@@ -31698,7 +31698,7 @@ from(<span class="code-quote">"timer:<sp
</div></div>
<h4><a shape="rect" name="BookInOnePage-UsingonConsume"></a>Using
onConsume</h4>
-<p>This component supports executing statements <b>after</b> data have been
consumed and processed by Camel. This allows you to do post updates in the
database. Notice all statements must be <tt>UPDATE</tt> statements. Camel
supports executing multiple statements whose name should be separated by
comma.</p>
+<p>This component supports executing statements <b>after</b> data have been
consumed and processed by Camel. This allows you to do post updates in the
database. Notice all statements must be <tt>UPDATE</tt> statements. Camel
supports executing multiple statements whose names should be separated by
commas.</p>
<p>The route below illustrates we execute the <b>consumeAccount</b> statement
data is processed. This allows us to change the status of the row in the
database to processed, so we avoid consuming it twice or more.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-2100-release.html
==============================================================================
--- websites/production/camel/content/camel-2100-release.html (original)
+++ websites/production/camel/content/camel-2100-release.html Fri Apr 6
16:20:36 2012
@@ -84,7 +84,7 @@
<p>Welcome to the 2.10.0 release with approximately XXX issues resolved -
including new features, improvements, and bug fixes, such as: </p>
-<ul><li>Internal code cleanup to reduce warnings reported by
Eclipse</li><li>Moved <a shape="rect" href="spring-testing.html" title="Spring
Testing">Spring Testing</a> from <tt>camel-test</tt> to
<tt>camel-test-spring</tt> component.</li><li>Camel <a shape="rect"
href="using-propertyplaceholder.html" title="Using
PropertyPlaceholder">Property Placeholders</a> are now supported in embedded <a
shape="rect" href="expression.html" title="Expression">Expression</a>s within
Camel routes.</li><li>Added missing options in the XML DSL for the <a
shape="rect" href="xpath.html" title="XPath">XPath</a> language to control and
set which XPath Engine to use, etc.</li><li>Added option <tt>logNamespaces</tt>
to the <a shape="rect" href="xpath.html" title="XPath">XPath</a> language to
have <tt>INFO</tt> logging of detected namespaces from message. This can be
used to troubleshoot issues where an <a shape="rect" href="xpath.html"
title="XPath">XPath</a> expression doesn't work as expected (a
s it's often a namespace conflict).</li><li>Added
<tt>replyToCacheLevelName</tt> option to the <a shape="rect" href="jms.html"
title="JMS">JMS</a> component, allowing configuration of cache levels for
persistent reply consumers when doing request/reply over JMS. Some message
brokers do not work well with caching, so users may need to set this option to
<tt>CACHE_NONE</tt>.</li><li>Added <tt>antInclude</tt> and <tt>antExclude</tt>
options to <a shape="rect" href="file2.html" title="File2">File</a> and <a
shape="rect" href="ftp2.html" title="FTP2">FTP</a> components to make it easier
to specify include/exclude filters using ANT syntax.</li><li>The <a
shape="rect" href="camel-maven-archetypes.html" title="Camel Maven
Archetypes">Camel archetypes</a> for Java and Scala no longer generate projects
with Spring dependencies.</li><li>Improved <tt>JdbcMessageIdRepository</tt> in
the <a shape="rect" href="sql-component.html" title="SQL Component">SQL</a> to
use custom SQL statements/q
ueries.</li><li>Added option to <a shape="rect" href="properties.html"
title="Properties">Properties</a> to allow silently ignoring property locations
not found, such as a .properties file.</li><li>Added
<tt>managementNamePattern</tt> attribute to <tt><camelContext></tt> to
make it very easy to customize and control the JMX naming of the Camel
application. See details at <a shape="rect"
href="camel-jmx.html#CamelJMX-CamelJMXManagementNamingStrategy">Camel JMX</a>.
For example, in OSGi environments you can explicitly configure a
<tt>managementNamePattern</tt> in case you do not want the bundleId as part of
MBean names.</li><li>Added streaming update support to <a shape="rect"
href="solr.html" title="Solr">Solr</a> as well as support for
SolrInputDocuments</li><li>Added SolrJ DirectXMLRequest support to <a
shape="rect" href="solr.html" title="Solr">Solr</a> to support XML based index
updates</li><li>Improved Camel <a shape="rect" href="mail.html"
title="Mail">Mail</a> to
support the <tt>replyTo</tt> option</li><li>Added <tt>traceEnabled</tt>
option to <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> component
so you have control over whether to allow HTTP TRACE calls against your Jetty
endpoints.</li><li>Polished the <a shape="rect"
href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven
Archetypes</a> to let the projects be prepared for <a shape="rect"
href="testing.html" title="Testing">Testing</a>, and fixed any WARNs from
Maven.</li><li>Added <tt>dumpRouteStatsAsXml</tt> methods to <a shape="rect"
href="camel-jmx.html" title="Camel JMX">JMX</a> to make it easier to get the
total performance stats as XML, and in one JMX call.</li><li><a shape="rect"
href="graceful-shutdown.html" title="Graceful Shutdown">Graceful Shutdown</a>
is now more aggressive if timeout occurred during shutdown, rejecting continued
processing of messages or redeliveries.</li><li>Add <tt>ShutdownPrepared</tt>
SPI to allow custom Servic
es (also EIPs) in routes to do custom code in preparation for
shutdown.</li><li>The <tt>camel-archetype-java</tt> <a shape="rect"
href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven
Archetypes</a> is now a pure Java DSL based project (no longer
Spring)</li><li><a shape="rect" href="jms.html" title="JMS">JMS</a> consumer is
less verbose when logging uncaught exceptions thrown while processing a
message. Added <tt>errorHandlerLoggingLevel</tt>, and
<tt>errorHandlerLogStackTrace</tt> options to tweak the logging
verbosity.</li><li>Added <tt>messageId</tt> as an <a shape="rect"
href="mdc-logging.html" title="MDC logging">MDC logging</a>
key.</li><li>Improved Camel's Transaction <a shape="rect"
href="error-handler.html" title="Error Handler">Error Handler</a> logging to
better pinpoint and correlate redelivered messages (from, e.g., a JMS broker),
making the logs much easier to read.</li><li>Added a timeout option to <a
shape="rect" href="spring-web-serv
ices.html" title="Spring Web Services">Spring Web Services</a> for specifying
the read timeout while invoking a webservice.</li><li>Optimized <a shape="rect"
href="type-converter.html" title="Type Converter">Type Converter</a> registry
for possible concurrency contention when looking up a type
converter.</li><li>Improved <a shape="rect" href="simple.html"
title="Simple">Simple</a> language to work better with floating point numbers
in <a shape="rect" href="predicate.html"
title="Predicate">Predicate</a>s</li><li>Camel is now less verbose when
starting and stopping, with less being logged at <tt>INFO</tt>
level.</li><li>Add support for keyed data queues to <a shape="rect"
href="jt400.html" title="JT400">JT400</a> component.</li><li><a shape="rect"
href="idempotent-consumer.html" title="Idempotent Consumer">Idempotent
Consumer</a> is now enlisted in JMX, which allows monitoring the duplicate
message count as well as the operation to reset it.</li><li>Thread pools
registered in
<a shape="rect" href="camel-jmx.html" title="Camel JMX">JMX</a> are now
unregistered when Camel shuts them down. Note that all MBeans will be
unregistered from JMX when Camel shuts itself down. This improvement is to
unregister thread pools more eagerly, such as when routes are removed at
runtime.</li><li>Camel will now also copy the message headers for a
<tt>JmsMessage</tt> if you leverage <tt>useOriginalMessage</tt> in an
<tt>onException</tt> definition.</li><li>Added <tt>mockEndpointsAndSkip</tt> to
<a shape="rect" href="advicewith.html" title="AdviceWith">AdviceWith</a> and
the <a shape="rect" href="testing.html" title="Testing">Test
Kit</a></li><li>The <a shape="rect" href="file2.html" title="File2">File</a>
and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components now
support filtering directories. The <tt>isDirectory</tt> method on the
<tt>GenericFile</tt> class can be used to skip unwanted directories,
accelerating file consumption.</li><li><a shape="rect
" href="smpp.html" title="SMPP">SMPP</a> connections can now be tunneled
through an HTTP proxy by configuring HTTP proxy settings.</li><li>Camel now
also checks, when starting a route dynamically, whether there would be any
violations on multiple consumers from the same <a shape="rect"
href="endpoint.html" title="Endpoint">Endpoint</a>. Previously this check only
occurred during Camel startup - now it always happens.</li><li>Stopping a
<tt>ConsumerTemplate</tt> or a <tt>ProducerTemplate</tt> will now stop and
shutdown its cache to cleanup any resources which otherwise may not have been
reclaimed until shutdown.</li><li><a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/ScheduledPollConsumer.html";>ScheduledPollConsumer</a>
will now shutdown thread pools more eagerly, such as when stopping a
<tt>ConsumerTemplate</tt>.</li><li>Added option <tt>asyncStartListener</tt> to
<a shape="rect" href="jms.html" title
="JMS">JMS</a> to allow starting JMS consumers (e.g. routes) asynchronously.
This can be used to avoid blocking in case the JMS consumer takes long time to
establish a connection to the JMS broker.</li><li><a shape="rect"
href="wire-tap.html" title="Wire Tap">Wire Tap</a> now supports <a shape="rect"
href="error-handling-in-camel.html" title="Error handling in Camel">Error
Handling</a> when sending a tapped message to an <a shape="rect"
href="endpoint.html" title="Endpoint">Endpoint</a>.</li><li>Added the
autogenColumns, configRef and strategyRef options to the <a shape="rect"
href="csv.html" title="CSV">CSV</a> dataformat in XML DSL.</li><li><a
shape="rect" href="validation.html" title="Validation">Validator</a> component
will now fail with a better error message if resource schema refers to element
which cannot be resolved.</li><li>Added support for retrieving generated keys
from <a shape="rect" href="jdbc.html" title="JDBC">JDBC</a>
component.</li><li>Added support for Sp
ring 3.1.x.</li><li>Added <tt>retainFirst</tt>, and <tt>retainLast</tt>
options to <a shape="rect" href="mock.html" title="Mock">Mock</a>
component.</li><li>Improved <a shape="rect" href="simple.html"
title="Simple">Simple</a> language to allow referring to headers using bracket
notation.</li><li>Added support for the scp: protocol via <a shape="rect"
href="jsch.html" title="Jsch">Jsch</a>.</li><li>Added support to exclude
certain fields when marshalling POJO's to <a shape="rect" href="json.html"
title="JSON">JSON</a>. Available with both the Jackson and GSON
library.</li><li>Allow to configure frequency of timeout checker when doing
request/reply over <a shape="rect" href="jms.html" title="JMS">JMS</a></li></ul>
+<ul><li>Internal code cleanup to reduce warnings reported by
Eclipse</li><li>Moved <a shape="rect" href="spring-testing.html" title="Spring
Testing">Spring Testing</a> from <tt>camel-test</tt> to
<tt>camel-test-spring</tt> component.</li><li>Camel <a shape="rect"
href="using-propertyplaceholder.html" title="Using
PropertyPlaceholder">Property Placeholders</a> are now supported in embedded <a
shape="rect" href="expression.html" title="Expression">Expression</a>s within
Camel routes.</li><li>Added missing options in the XML DSL for the <a
shape="rect" href="xpath.html" title="XPath">XPath</a> language to control and
set which XPath Engine to use, etc.</li><li>Added option <tt>logNamespaces</tt>
to the <a shape="rect" href="xpath.html" title="XPath">XPath</a> language to
have <tt>INFO</tt> logging of detected namespaces from message. This can be
used to troubleshoot issues where an <a shape="rect" href="xpath.html"
title="XPath">XPath</a> expression doesn't work as expected (a
s it's often a namespace conflict).</li><li>Added
<tt>replyToCacheLevelName</tt> option to the <a shape="rect" href="jms.html"
title="JMS">JMS</a> component, allowing configuration of cache levels for
persistent reply consumers when doing request/reply over JMS. Some message
brokers do not work well with caching, so users may need to set this option to
<tt>CACHE_NONE</tt>.</li><li>Added <tt>antInclude</tt> and <tt>antExclude</tt>
options to <a shape="rect" href="file2.html" title="File2">File</a> and <a
shape="rect" href="ftp2.html" title="FTP2">FTP</a> components to make it easier
to specify include/exclude filters using ANT syntax.</li><li>The <a
shape="rect" href="camel-maven-archetypes.html" title="Camel Maven
Archetypes">Camel archetypes</a> for Java and Scala no longer generate projects
with Spring dependencies.</li><li>Improved <tt>JdbcMessageIdRepository</tt> in
the <a shape="rect" href="sql-component.html" title="SQL Component">SQL</a> to
use custom SQL statements/q
ueries.</li><li>Added option to <a shape="rect" href="properties.html"
title="Properties">Properties</a> to allow silently ignoring property locations
not found, such as a .properties file.</li><li>Added
<tt>managementNamePattern</tt> attribute to <tt><camelContext></tt> to
make it very easy to customize and control the JMX naming of the Camel
application. See details at <a shape="rect"
href="camel-jmx.html#CamelJMX-CamelJMXManagementNamingStrategy">Camel JMX</a>.
For example, in OSGi environments you can explicitly configure a
<tt>managementNamePattern</tt> in case you do not want the bundleId as part of
MBean names.</li><li>Added streaming update support to <a shape="rect"
href="solr.html" title="Solr">Solr</a> as well as support for
SolrInputDocuments</li><li>Added SolrJ DirectXMLRequest support to <a
shape="rect" href="solr.html" title="Solr">Solr</a> to support XML based index
updates</li><li>Improved Camel <a shape="rect" href="mail.html"
title="Mail">Mail</a> to
support the <tt>replyTo</tt> option</li><li>Added <tt>traceEnabled</tt>
option to <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> component
so you have control over whether to allow HTTP TRACE calls against your Jetty
endpoints.</li><li>Polished the <a shape="rect"
href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven
Archetypes</a> to let the projects be prepared for <a shape="rect"
href="testing.html" title="Testing">Testing</a>, and fixed any WARNs from
Maven.</li><li>Added <tt>dumpRouteStatsAsXml</tt> methods to <a shape="rect"
href="camel-jmx.html" title="Camel JMX">JMX</a> to make it easier to get the
total performance stats as XML, and in one JMX call.</li><li><a shape="rect"
href="graceful-shutdown.html" title="Graceful Shutdown">Graceful Shutdown</a>
is now more aggressive if timeout occurred during shutdown, rejecting continued
processing of messages or redeliveries.</li><li>Add <tt>ShutdownPrepared</tt>
SPI to allow custom Servic
es (also EIPs) in routes to do custom code in preparation for
shutdown.</li><li>The <tt>camel-archetype-java</tt> <a shape="rect"
href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven
Archetypes</a> is now a pure Java DSL based project (no longer
Spring)</li><li><a shape="rect" href="jms.html" title="JMS">JMS</a> consumer is
less verbose when logging uncaught exceptions thrown while processing a
message. Added <tt>errorHandlerLoggingLevel</tt>, and
<tt>errorHandlerLogStackTrace</tt> options to tweak the logging
verbosity.</li><li>Added <tt>messageId</tt> as an <a shape="rect"
href="mdc-logging.html" title="MDC logging">MDC logging</a>
key.</li><li>Improved Camel's Transaction <a shape="rect"
href="error-handler.html" title="Error Handler">Error Handler</a> logging to
better pinpoint and correlate redelivered messages (from, e.g., a JMS broker),
making the logs much easier to read.</li><li>Added a timeout option to <a
shape="rect" href="spring-web-serv
ices.html" title="Spring Web Services">Spring Web Services</a> for specifying
the read timeout while invoking a webservice.</li><li>Optimized <a shape="rect"
href="type-converter.html" title="Type Converter">Type Converter</a> registry
for possible concurrency contention when looking up a type
converter.</li><li>Improved <a shape="rect" href="simple.html"
title="Simple">Simple</a> language to work better with floating point numbers
in <a shape="rect" href="predicate.html"
title="Predicate">Predicate</a>s</li><li>Camel is now less verbose when
starting and stopping, with less being logged at <tt>INFO</tt>
level.</li><li>Add support for keyed data queues to <a shape="rect"
href="jt400.html" title="JT400">JT400</a> component.</li><li><a shape="rect"
href="idempotent-consumer.html" title="Idempotent Consumer">Idempotent
Consumer</a> is now enlisted in JMX, which allows monitoring the duplicate
message count as well as the operation to reset it.</li><li>Thread pools
registered in
<a shape="rect" href="camel-jmx.html" title="Camel JMX">JMX</a> are now
unregistered when Camel shuts them down. Note that all MBeans will be
unregistered from JMX when Camel shuts itself down. This improvement is to
unregister thread pools more eagerly, such as when routes are removed at
runtime.</li><li>Camel will now also copy the message headers for a
<tt>JmsMessage</tt> if you leverage <tt>useOriginalMessage</tt> in an
<tt>onException</tt> definition.</li><li>Added <tt>mockEndpointsAndSkip</tt> to
<a shape="rect" href="advicewith.html" title="AdviceWith">AdviceWith</a> and
the <a shape="rect" href="testing.html" title="Testing">Test
Kit</a></li><li>The <a shape="rect" href="file2.html" title="File2">File</a>
and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components now
support filtering directories. The <tt>isDirectory</tt> method on the
<tt>GenericFile</tt> class can be used to skip unwanted directories,
accelerating file consumption.</li><li><a shape="rect
" href="smpp.html" title="SMPP">SMPP</a> connections can now be tunneled
through an HTTP proxy by configuring HTTP proxy settings.</li><li>Camel now
also checks, when starting a route dynamically, whether there would be any
violations on multiple consumers from the same <a shape="rect"
href="endpoint.html" title="Endpoint">Endpoint</a>. Previously this check only
occurred during Camel startup - now it always happens.</li><li>Stopping a
<tt>ConsumerTemplate</tt> or a <tt>ProducerTemplate</tt> will now stop and
shutdown its cache to cleanup any resources which otherwise may not have been
reclaimed until shutdown.</li><li><a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/ScheduledPollConsumer.html";>ScheduledPollConsumer</a>
will now shutdown thread pools more eagerly, such as when stopping a
<tt>ConsumerTemplate</tt>.</li><li>Added option <tt>asyncStartListener</tt> to
<a shape="rect" href="jms.html" title
="JMS">JMS</a> to allow starting JMS consumers (e.g. routes) asynchronously.
This can be used to avoid blocking in case the JMS consumer takes long time to
establish a connection to the JMS broker.</li><li><a shape="rect"
href="wire-tap.html" title="Wire Tap">Wire Tap</a> now supports <a shape="rect"
href="error-handling-in-camel.html" title="Error handling in Camel">Error
Handling</a> when sending a tapped message to an <a shape="rect"
href="endpoint.html" title="Endpoint">Endpoint</a>.</li><li>Added the
autogenColumns, configRef and strategyRef options to the <a shape="rect"
href="csv.html" title="CSV">CSV</a> dataformat in XML DSL.</li><li><a
shape="rect" href="validation.html" title="Validation">Validator</a> component
will now fail with a better error message if resource schema refers to element
which cannot be resolved.</li><li>Added support for retrieving generated keys
from <a shape="rect" href="jdbc.html" title="JDBC">JDBC</a>
component.</li><li>Added support for Sp
ring 3.1.x.</li><li>Added <tt>retainFirst</tt>, and <tt>retainLast</tt>
options to <a shape="rect" href="mock.html" title="Mock">Mock</a>
component.</li><li>Improved <a shape="rect" href="simple.html"
title="Simple">Simple</a> language to allow referring to headers using bracket
notation.</li><li>Added support for the scp: protocol via <a shape="rect"
href="jsch.html" title="Jsch">Jsch</a>.</li><li>Added support to exclude
certain fields when marshalling POJO's to <a shape="rect" href="json.html"
title="JSON">JSON</a>. Available with both the Jackson and GSON
library.</li><li>Allow to configure frequency of timeout checker when doing
request/reply over <a shape="rect" href="jms.html"
title="JMS">JMS</a></li><li>Improved the Java DSL to make it easier to use
predicates from the build-in DSL, that has commonly used predicates and
expressions.</li></ul>
<h3><a shape="rect" name="Camel2.10.0Release-Fixedissues"></a>Fixed issues</h3>
@@ -119,7 +119,7 @@
<h2><a shape="rect" name="Camel2.10.0Release-APIchanges%2Fbreaking"></a>API
changes/breaking</h2>
-<ul><li>Added <tt>shutdownForced</tt> and <tt>forceShutdown</tt> methods to
<tt>org.apache.camel.spi.ShutdownStrategy</tt></li><li>Add boolean parameter to
<tt>prepareShutdown</tt> on <tt>ShutdownAware</tt></li><li>The
<tt>errorHandler</tt> method in <tt>RouteBuilder</tt> now returns
<tt>void</tt>, as it's only used for configuring context-scoped error
handlers.</li><li>Removed the <tt>SimpleLanguage</tt> constructor that takes
custom start and end tokens. Instead use the change methods to set custom
tokens.</li><li>Added <tt>onThreadPoolRemove</tt> and
<tt>onErrorHandlerRemove</tt> methods to <tt>LifecycleStrategy</tt></li></ul>
+<ul><li>Added <tt>shutdownForced</tt> and <tt>forceShutdown</tt> methods to
<tt>org.apache.camel.spi.ShutdownStrategy</tt></li><li>Add boolean parameter to
<tt>prepareShutdown</tt> on <tt>ShutdownAware</tt></li><li>The
<tt>errorHandler</tt> method in <tt>RouteBuilder</tt> now returns
<tt>void</tt>, as it's only used for configuring context-scoped error
handlers.</li><li>Removed the <tt>SimpleLanguage</tt> constructor that takes
custom start and end tokens. Instead use the change methods to set custom
tokens.</li><li>Added <tt>onThreadPoolRemove</tt> and
<tt>onErrorHandlerRemove</tt> methods to
<tt>LifecycleStrategy</tt></li><li>Removed <tt>retryWhile(Expression)</tt> on
<tt>OnExceptionDefinition</tt>; use <tt>retryWhile(Predicate)</tt>.</li></ul>
<h2><a shape="rect"
name="Camel2.10.0Release-Internal%2FNonAPIrefactoringsthatmayaffectusers"></a>Internal/Non
API refactorings that may affect users</h2>
Modified: websites/production/camel/content/mybatis.html
==============================================================================
--- websites/production/camel/content/mybatis.html (original)
+++ websites/production/camel/content/mybatis.html Fri Apr 6 16:20:36 2012
@@ -104,12 +104,12 @@ mybatis:statementName[?options]
<p>You can append query options to the URI in the following format,
<tt>?option=value&option=value&...</tt></p>
-<p>This component will by default load the MyBatis SqlMapConfig file from the
root of the classpath and expected named as <tt>SqlMapConfig.xml</tt>.<br
clear="none">
-If the file is located in another location, you would have to configure the
<tt>configurationUri</tt> option on the <tt>MyBatisComponent</tt> component.</p>
+<p>This component will by default load the MyBatis SqlMapConfig file from the
root of the classpath with the expected name of <tt>SqlMapConfig.xml</tt>.<br
clear="none">
+If the file is located in another location, you will need to configure the
<tt>configurationUri</tt> option on the <tt>MyBatisComponent</tt> component.</p>
<h3><a shape="rect" name="MyBatis-Options"></a>Options</h3>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>consumer.onConsume</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Statements to run after consuming. Can be
used, for example, to update rows after they have been consumed and processed
in Camel. See sample later. Multiple statements can be separated with comma.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.useIterator</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluence
Td"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If
<tt>true</tt> each row returned when polling will be processed individually. If
<tt>false</tt> the entire <tt>List</tt> of data is set as the IN body.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.routeEmptyResultSet</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets whether empty result set should be routed or not. By
default, empty result sets are not routed. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>statementType</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>StatementType</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Mandatory to specify for producer to control
which kind of operation to
invoke. The enum values are: <tt>SelectOne</tt>, <tt>SelectList</tt>,
<tt>Insert</tt>, <tt>InsertList</tt>, <tt>Update</tt>, <tt>Delete</tt>.
<b>Notice:</b> <tt>InsertList</tt> is available as of Camel 2.10.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>maxMessagesPerPoll</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>int</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> An integer to define a maximum messages to gather per
poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to
avoid when starting up the server that there are thousands of files. Set a
value of 0 or negative to disabled it. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>consumer.onConsume</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Statements to run after consuming. Can be
used, for example, to update rows after they have been consumed and processed
in Camel. See sample later. Multiple statements can be separated with commas.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.useIterator</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenc
eTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If
<tt>true</tt> each row returned when polling will be processed individually. If
<tt>false</tt> the entire <tt>List</tt> of data is set as the IN body.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>consumer.routeEmptyResultSet</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets whether empty result sets should be routed.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>statementType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>StatementType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Mandatory
to specify for the producer to control which kind of operation to invoke. The
enum values are: <tt>SelectOne</tt>
, <tt>SelectList</tt>, <tt>Insert</tt>, <tt>InsertList</tt>, <tt>Update</tt>,
<tt>Delete</tt>. <b>Notice:</b> <tt>InsertList</tt> is available as of Camel
2.10. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>maxMessagesPerPoll</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>int</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> An integer to define the maximum messages to gather per
poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to
avoid when starting up the server that there are thousands of files. Set a
value of 0 or negative to disable it. </td></tr></tbody></table>
</div>
</div>
@@ -121,7 +121,7 @@ If the file is located in another locati
</div>
<h3><a shape="rect" name="MyBatis-MessageBody"></a>Message Body</h3>
-<p>The response from MyBatis will only be set as body if it's a
<tt>SELECT</tt> statement. That means, for example, for <tt>INSERT</tt>
statements Camel will not replace the body. This allows you to continue routing
and keep the original body. The response from MyBatis is always stored in the
header with the key <tt>CamelMyBatisResult</tt>.</p>
+<p>The response from MyBatis will only be set as the body if it's a
<tt>SELECT</tt> statement. That means, for example, for <tt>INSERT</tt>
statements Camel will not replace the body. This allows you to continue routing
and keep the original body. The response from MyBatis is always stored in the
header with the key <tt>CamelMyBatisResult</tt>.</p>
<h3><a shape="rect" name="MyBatis-Samples"></a>Samples</h3>
@@ -155,7 +155,7 @@ from(<span class="code-quote">"activemq:
</div></div>
<h3><a shape="rect"
name="MyBatis-UsingStatementTypeforbettercontrolofMyBatis"></a>Using
StatementType for better control of MyBatis</h3>
-<p>When routing to an MyBatis endpoint you want more fine grained control so
you can control whether the SQL statement to be executed is a <tt>SELEECT</tt>,
<tt>UPDATE</tt>, <tt>DELETE</tt> or <tt>INSERT</tt> etc. So for instance if we
want to route to an MyBatis endpoint in which the IN body contains parameters
to a <tt>SELECT</tt> statement we can do:</p>
+<p>When routing to an MyBatis endpoint you will want more fine grained control
so you can control whether the SQL statement to be executed is a
<tt>SELECT</tt>, <tt>UPDATE</tt>, <tt>DELETE</tt> or <tt>INSERT</tt> etc. So
for instance if we want to route to an MyBatis endpoint in which the IN body
contains parameters to a <tt>SELECT</tt> statement we can do:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">from(<span class="code-quote">"direct:start"</span>)
.to(<span
class="code-quote">"mybatis:selectAccountById?statementType=SelectOne"</span>)
@@ -173,7 +173,7 @@ from(<span class="code-quote">"activemq:
</pre>
</div></div>
-<p>And the same for <tt>UPDATE</tt>, where we can send an <tt>Account</tt>
object as IN body to MyBatis:</p>
+<p>And the same for <tt>UPDATE</tt>, where we can send an <tt>Account</tt>
object as the IN body to MyBatis:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">from(<span class="code-quote">"direct:start"</span>)
.to(<span
class="code-quote">"mybatis:updateAccount?statementType=Update"</span>)
@@ -233,7 +233,7 @@ from(<span class="code-quote">"timer:<sp
</div></div>
<h4><a shape="rect" name="MyBatis-UsingonConsume"></a>Using onConsume</h4>
-<p>This component supports executing statements <b>after</b> data have been
consumed and processed by Camel. This allows you to do post updates in the
database. Notice all statements must be <tt>UPDATE</tt> statements. Camel
supports executing multiple statements whose name should be separated by
comma.</p>
+<p>This component supports executing statements <b>after</b> data have been
consumed and processed by Camel. This allows you to do post updates in the
database. Notice all statements must be <tt>UPDATE</tt> statements. Camel
supports executing multiple statements whose names should be separated by
commas.</p>
<p>The route below illustrates we execute the <b>consumeAccount</b> statement
data is processed. This allows us to change the status of the row in the
database to processed, so we avoid consuming it twice or more.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
