Author: buildbot
Date: Tue Aug 26 09:19:04 2014
New Revision: 920441
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/ibatis.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 Tue Aug 26
09:19:04 2014
@@ -1529,11 +1529,11 @@ template.send("direct:alias-verify&
</div>
</div>
<p>The <strong>cxf:</strong> component provides integration with <a
shape="rect" href="http://cxf.apache.org";>Apache CXF</a> for connecting to
JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1408972730480 {padding: 0px;}
-div.rbtoc1408972730480 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1408972730480 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1409044661949 {padding: 0px;}
+div.rbtoc1409044661949 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1409044661949 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1408972730480">
+/*]]>*/</style></p><div class="toc-macro rbtoc1409044661949">
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF
Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI
format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#CXF-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
@@ -5470,84 +5470,30 @@ httpComponent.setHttpClientConfigurer(ne
]]></script>
</div></div><p>As long as you implement the HttpClientConfigurer and configure
your keystore and truststore as described above, it will work
fine.</p><p></p><h3 id="BookComponentAppendix-SeeAlso.22">See Also</h3>
<ul><li><a shape="rect" href="configuring-camel.html">Configuring
Camel</a></li><li><a shape="rect"
href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect"
href="getting-started.html">Getting Started</a></li></ul><ul
class="alternate"><li><a shape="rect" href="jetty.html">Jetty</a></li></ul>
-<h2 id="BookComponentAppendix-iBATIS">iBATIS</h2>
-
-<p>The <strong>ibatis:</strong> component allows you to query, poll, insert,
update and delete data in a relational database using <a shape="rect"
class="external-link" href="http://ibatis.apache.org/";>Apache iBATIS</a>.</p>
-
- <div class="aui-message problem shadowed information-macro">
+<h2 id="BookComponentAppendix-iBATIS">iBATIS</h2><p>The
<strong>ibatis:</strong> component allows you to query, poll, insert, update
and delete data in a relational database using <a shape="rect"
class="external-link" href="http://ibatis.apache.org/";>Apache iBATIS</a>.</p>
<div class="aui-message problem shadowed information-macro">
<p class="title">Prefer MyBatis</p>
<span class="aui-icon icon-problem">Icon</span>
<div class="message-content">
-
-<p>The Apache iBatis project is no longer active. The project is moved outside
Apache and is now know as the MyBatis project.<br clear="none">
-Therefore we encourage users to use <a shape="rect"
href="mybatis.html">MyBatis</a> instead. This camel-ibatis component will be
removed in Camel 3.0.</p>
+ <p>The Apache iBatis project is no longer active.
The project is moved outside Apache and is now know as the MyBatis project.<br
clear="none">Therefore we encourage users to use <a shape="rect"
href="mybatis.html">MyBatis</a> instead. This camel-ibatis component will be
removed in Camel 3.0.</p><p>iBatis do not support Spring 4.x. So you can only
use Spring 3.x or older with iBatis.</p>
</div>
</div>
-
-
-<p>Maven users will need to add the following dependency to their
<code>pom.xml</code> for this component:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<dependency>
+<p>Maven users will need to add the following dependency to their
<code>pom.xml</code> for this component:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-ibatis</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
]]></script>
-</div></div>
-
-<h3 id="BookComponentAppendix-URIformat.27">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-ibatis:statementName[?options]
+</div></div><h3 id="BookComponentAppendix-URIformat.27">URI format</h3><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[ibatis:statementName[?options]
]]></script>
-</div></div>
-
-<p>Where <strong>statementName</strong> is the name in the iBATIS XML
configuration file which maps to the query, insert, update or delete operation
you wish to evaluate.</p>
-
-<p>You can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p>
-
-<p>This component will by default load the iBatis SqlMapConfig file from the
root of the classpath and expected named as <code>SqlMapConfig.xml</code>.<br
clear="none">
-It uses Spring resource loading so you can define it using
<code>classpath</code>, <code>file</code> or <code>http</code> as prefix to
load resources with those schemes.<br clear="none">
-In Camel 2.2 you can configure this on the iBatisComponent with the
<code>setSqlMapConfig(String)</code> method.</p>
-
-<h3 id="BookComponentAppendix-Options.22">Options</h3>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Option </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>consumer.onConsume</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> 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.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>consumer.useIterator</code> </p></td><td colspan="1" rowspa
n="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> If <code>true</code> each row returned
when polling will be processed individually. If <code>false</code> the entire
<code>List</code> of data is set as the IN body. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>consumer.routeEmptyResultSet</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Sets whether empty result set
should be routed or not. By default, empty result sets are not routed.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>statementType</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>StatementType</code> </p></td><
td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Mandatory to
specify for IbatisProducer to control which iBatis <code>SqlMapClient</code>
method to invoke. The enum values are: <code>QueryForObject</code>,
<code>QueryForList</code>, <code>Insert</code>, <code>Update</code>,
<code>Delete</code>. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>maxMessagesPerPoll</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> 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.
</p></td></tr><tr><td colspan="1" rowspan="1" cl
ass="confluenceTd"><p> <code>isolation</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>TRANSACTION_REPEATABLE_READ</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.9:</strong> A String the defines the
transaction isolation level of the will be used. Allowed values are
TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED,
TRANSACTION_REPEATABLE_READ, TRANSACTION_SERIALIZABLE
</p></td></tr></tbody></table></div>
-
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>isolation</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>String</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>TRANSACTION_REPEATABLE_READ</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9:</strong> A
String the defines the transaction isolation level of the will be used. Allowed
values are TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED,
TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ,
TRANSACTION_SERIALIZABLE </p></td></tr></tbody></table></div>
-
-</div>
-
-<h3 id="BookComponentAppendix-MessageHeaders.7">Message Headers</h3>
-<p>Camel will populate the result message, either IN or OUT with a header with
the operationName used:</p>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Header </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>CamelIBatisStatementName</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> The <strong>statementName</strong> used
(for example: insertAccount). </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>CamelIBatisResult</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>Object</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The
<strong>response</strong> returned from iBatis in any of the operations. For
instance an <code>INSERT</code> could return the auto-generated key, or number o
f rows etc. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="BookComponentAppendix-MessageBody.2">Message Body</h3>
-<p>The response from iBatis will only be set as body if it's a
<code>SELECT</code> statement. That means, for example, for <code>INSERT</code>
statements Camel will not replace the body. This allows you to continue routing
and keep the original body. The response from iBatis is always stored in the
header with the key <code>CamelIBatisResult</code>.</p>
-
-<h3 id="BookComponentAppendix-Samples.5">Samples</h3>
-
-<p>For example if you wish to consume beans from a JMS queue and insert them
into a database you could do the following:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-from("activemq:queue:newAccount").
+</div></div><p>Where <strong>statementName</strong> is the name in the iBATIS
XML configuration file which maps to the query, insert, update or delete
operation you wish to evaluate.</p><p>You can append query options to the URI
in the following format,
<code>?option=value&option=value&...</code></p><p>This component will
by default load the iBatis SqlMapConfig file from the root of the classpath and
expected named as <code>SqlMapConfig.xml</code>.<br clear="none"> It uses
Spring resource loading so you can define it using <code>classpath</code>,
<code>file</code> or <code>http</code> as prefix to load resources with those
schemes.<br clear="none"> In Camel 2.2 you can configure this on the
iBatisComponent with the <code>setSqlMapConfig(String)</code> method.</p><h3
id="BookComponentAppendix-Options.22">Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Option</p>
</th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>consumer.onConsume</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>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.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>consumer.useIterator</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colsp
an="1" rowspan="1" class="confluenceTd"><p>If <code>true</code> each row
returned when polling will be processed individually. If <code>false</code> the
entire <code>List</code> of data is set as the IN body.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>consumer.routeEmptyResultSet</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Sets whether empty result set should be
routed or not. By default, empty result sets are not
routed.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>statementType</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>StatementType</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Mandatory to specify for
IbatisProd
ucer to control which iBatis <code>SqlMapClient</code> method to invoke. The
enum values are: <code>QueryForObject</code>, <code>QueryForList</code>,
<code>Insert</code>, <code>Update</code>,
<code>Delete</code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxMessagesPerPoll</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>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.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>isolation</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluen
ceTd"><p><code>TRANSACTION_REPEATABLE_READ</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> A String the
defines the transaction isolation level of the will be used. Allowed values are
TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED,
TRANSACTION_REPEATABLE_READ,
TRANSACTION_SERIALIZABLE</p></td></tr></tbody></table></div><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>isolation</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>TRANSACTION_REPEATABLE_READ</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> A
String the defines the transaction isolation level of the will be used. Allowed
values are TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED,
TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE
_READ, TRANSACTION_SERIALIZABLE</p></td></tr></tbody></table></div></div><h3
id="BookComponentAppendix-MessageHeaders.7">Message Headers</h3><p>Camel will
populate the result message, either IN or OUT with a header with the
operationName used:</p><div class="confluenceTableSmall"><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Header</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>CamelIBatisStatementName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The
<strong>statementName</strong> used (for example:
insertAccount).</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>CamelIBatisResult</code></p></td><td colspan="1"
rowspan="1" c
lass="confluenceTd"><p><code>Object</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>The <strong>response</strong> returned from iBatis in
any of the operations. For instance an <code>INSERT</code> could return the
auto-generated key, or number of rows
etc.</p></td></tr></tbody></table></div></div><h3
id="BookComponentAppendix-MessageBody.2">Message Body</h3><p>The response from
iBatis will only be set as body if it's a <code>SELECT</code> statement. That
means, for example, for <code>INSERT</code> statements Camel will not replace
the body. This allows you to continue routing and keep the original body. The
response from iBatis is always stored in the header with the key
<code>CamelIBatisResult</code>.</p><h3
id="BookComponentAppendix-Samples.5">Samples</h3><p>For example if you wish to
consume beans from a JMS queue and insert them into a database you could do the
following:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelCo
ntent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("activemq:queue:newAccount").
to("ibatis:insertAccount?statementType=Insert");
]]></script>
-</div></div>
-
-<p>Notice we have to specify the <code>statementType</code>, as we need to
instruct Camel which <code>SqlMapClient</code> operation to invoke.</p>
-
-<p>Where <strong>insertAccount</strong> is the iBatis ID in the SQL map
file:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
- <!-- Insert example, using the Account parameter class -->
+</div></div><p>Notice we have to specify the <code>statementType</code>, as we
need to instruct Camel which <code>SqlMapClient</code> operation to
invoke.</p><p>Where <strong>insertAccount</strong> is the iBatis ID in the SQL
map file:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[ <!-- Insert example, using the Account
parameter class -->
<insert id="insertAccount"
parameterClass="Account">
insert into ACCOUNT (
ACC_ID,
@@ -5560,88 +5506,51 @@ from("activemq:queue:newAccount&quo
)
</insert>
]]></script>
-</div></div>
-
-<h3
id="BookComponentAppendix-UsingStatementTypeforbettercontrolofIBatis">Using
StatementType for better control of IBatis</h3>
-<p>When routing to an iBatis endpoint you want more fine grained control so
you can control whether the SQL statement to be executed is a
<code>SELEECT</code>, <code>UPDATE</code>, <code>DELETE</code> or
<code>INSERT</code> etc. So for instance if we want to route to an iBatis
endpoint in which the IN body contains parameters to a <code>SELECT</code>
statement we can do:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><h3
id="BookComponentAppendix-UsingStatementTypeforbettercontrolofIBatis">Using
StatementType for better control of IBatis</h3><p>When routing to an iBatis
endpoint you want more fine grained control so you can control whether the SQL
statement to be executed is a <code>SELEECT</code>, <code>UPDATE</code>,
<code>DELETE</code> or <code>INSERT</code> etc. So for instance if we want to
route to an iBatis endpoint in which the IN body contains parameters to a
<code>SELECT</code> statement we can do:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from("direct:start")
.to("ibatis:selectAccountById?statementType=QueryForObject")
.to("mock:result");
]]></script>
-</div></div>
-
-<p>In the code above we can invoke the iBatis statement
<code>selectAccountById</code> and the IN body should contain the account id we
want to retrieve, such as an <code>Integer</code> type.</p>
-
-<p>We can do the same for some of the other operations, such as
<code>QueryForList</code>:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>In the code above we can invoke the iBatis statement
<code>selectAccountById</code> and the IN body should contain the account id we
want to retrieve, such as an <code>Integer</code> type.</p><p>We can do the
same for some of the other operations, such as
<code>QueryForList</code>:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from("direct:start")
.to("ibatis:selectAllAccounts?statementType=QueryForList")
.to("mock:result");
]]></script>
-</div></div>
-
-<p>And the same for <code>UPDATE</code>, where we can send an
<code>Account</code> object as IN body to iBatis:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>And the same for <code>UPDATE</code>, where we can send an
<code>Account</code> object as IN body to iBatis:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from("direct:start")
.to("ibatis:updateAccount?statementType=Update")
.to("mock:result");
]]></script>
-</div></div>
-
-
-<h4 id="BookComponentAppendix-Scheduledpollingexample">Scheduled polling
example</h4>
-<p>Since this component does not support scheduled polling, you need to use
another mechanism for triggering the scheduled polls, such as the <a
shape="rect" href="timer.html">Timer</a> or <a shape="rect"
href="quartz.html">Quartz</a> components.</p>
-
-<p>In the sample below we poll the database, every 30 seconds using the <a
shape="rect" href="timer.html">Timer</a> component and send the data to the JMS
queue:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-from("timer://pollTheDatabase?delay=30000").to("ibatis:selectAllAccounts?statementType=QueryForList").to("activemq:queue:allAccounts");
+</div></div><h4 id="BookComponentAppendix-Scheduledpollingexample">Scheduled
polling example</h4><p>Since this component does not support scheduled polling,
you need to use another mechanism for triggering the scheduled polls, such as
the <a shape="rect" href="timer.html">Timer</a> or <a shape="rect"
href="quartz.html">Quartz</a> components.</p><p>In the sample below we poll the
database, every 30 seconds using the <a shape="rect"
href="timer.html">Timer</a> component and send the data to the JMS
queue:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("timer://pollTheDatabase?delay=30000").to("ibatis:selectAllAccounts?statementType=QueryForList").to("activemq:queue:allAccounts");
]]></script>
-</div></div>
-
-<p>And the iBatis SQL map file used:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
- <!-- Select with no parameters using the result map for Account class.
-->
+</div></div><p>And the iBatis SQL map file used:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[ <!-- Select with no parameters using the
result map for Account class. -->
<select id="selectAllAccounts"
resultMap="AccountResult">
select * from ACCOUNT
</select>
]]></script>
-</div></div>
-
-<h4 id="BookComponentAppendix-UsingonConsume">Using onConsume</h4>
-<p>This component supports executing statements <strong>after</strong> data
have been consumed and processed by Camel. This allows you to do post updates
in the database. Notice all statements must be <code>UPDATE</code> statements.
Camel supports executing multiple statements whose name should be separated by
comma.</p>
-
-<p>The route below illustrates we execute the <strong>consumeAccount</strong>
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 pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><h4 id="BookComponentAppendix-UsingonConsume">Using
onConsume</h4><p>This component supports executing statements
<strong>after</strong> data have been consumed and processed by Camel. This
allows you to do post updates in the database. Notice all statements must be
<code>UPDATE</code> statements. Camel supports executing multiple statements
whose name should be separated by comma.</p><p>The route below illustrates we
execute the <strong>consumeAccount</strong> 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 pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from("ibatis:selectUnprocessedAccounts?consumer.onConsume=consumeAccount").to("mock:results");
]]></script>
-</div></div>
-
-<p>And the statements in the sqlmap file:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>And the statements in the sqlmap file:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
<select id="selectUnprocessedAccounts"
resultMap="AccountResult">
select * from ACCOUNT where PROCESSED = false
</select>
]]></script>
-</div></div>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
<update id="consumeAccount" parameterClass="Account">
update ACCOUNT set PROCESSED = true where ACC_ID = #id#
</update>
]]></script>
-</div></div>
-
-<h3 id="BookComponentAppendix-SeeAlso.23">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring
Camel</a></li><li><a shape="rect"
href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect"
href="getting-started.html">Getting Started</a></li></ul>
-<ul class="alternate"><li><a shape="rect"
href="mybatis.html">MyBatis</a></li></ul>
+</div></div><p></p><h3 id="BookComponentAppendix-SeeAlso.23">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring
Camel</a></li><li><a shape="rect"
href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect"
href="getting-started.html">Getting Started</a></li></ul><ul
class="alternate"><li><a shape="rect" href="mybatis.html">MyBatis</a></li></ul>
<h2 id="BookComponentAppendix-IRCComponent">IRC Component</h2>
<p>The <strong>irc</strong> component implements an <a shape="rect"
class="external-link" href="http://en.wikipedia.org/wiki/Internet_Relay_Chat";
rel="nofollow">IRC</a> (Internet Relay Chat) transport.</p>
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Tue Aug 26 09:19:04
2014
@@ -4158,11 +4158,11 @@ While not actual tutorials you might fin
</div>
</div>
<h2 id="BookInOnePage-Preface">Preface</h2><p>This tutorial aims to guide the
reader through the stages of creating a project which uses Camel to facilitate
the routing of messages from a JMS queue to a <a shape="rect"
class="external-link" href="http://www.springramework.org";
rel="nofollow">Spring</a> service. The route works in a synchronous fashion
returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1408972741863 {padding: 0px;}
-div.rbtoc1408972741863 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1408972741863 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1409044676266 {padding: 0px;}
+div.rbtoc1409044676266 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1409044676266 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1408972741863">
+/*]]>*/</style></p><div class="toc-macro rbtoc1409044676266">
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-JmsRemoting-TutorialonSpringRemotingwithJMS">Tutorial on Spring
Remoting with JMS</a></li><li><a shape="rect"
href="#Tutorial-JmsRemoting-Preface">Preface</a></li><li><a shape="rect"
href="#Tutorial-JmsRemoting-Prerequisites">Prerequisites</a></li><li><a
shape="rect"
href="#Tutorial-JmsRemoting-Distribution">Distribution</a></li><li><a
shape="rect" href="#Tutorial-JmsRemoting-About">About</a></li><li><a
shape="rect" href="#Tutorial-JmsRemoting-CreatetheCamelProject">Create the
Camel Project</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-JmsRemoting-UpdatethePOMwithDependencies">Update the POM with
Dependencies</a></li></ul>
</li><li><a shape="rect" href="#Tutorial-JmsRemoting-WritingtheServer">Writing
the Server</a>
@@ -6348,11 +6348,11 @@ So we completed the last piece in the pi
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1408972742189 {padding: 0px;}
-div.rbtoc1408972742189 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1408972742189 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1409044676552 {padding: 0px;}
+div.rbtoc1409044676552 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1409044676552 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1408972742189">
+/*]]>*/</style><div class="toc-macro rbtoc1409044676552">
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-AXIS-Camel-TutorialusingAxis1.4withApacheCamel">Tutorial using
Axis 1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-AXIS-Camel-Prerequisites">Prerequisites</a></li><li><a
shape="rect"
href="#Tutorial-AXIS-Camel-Distribution">Distribution</a></li><li><a
shape="rect"
href="#Tutorial-AXIS-Camel-Introduction">Introduction</a></li><li><a
shape="rect" href="#Tutorial-AXIS-Camel-SettinguptheprojecttorunAxis">Setting
up the project to run Axis</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-AXIS-Camel-Maven2">Maven 2</a></li><li><a shape="rect"
href="#Tutorial-AXIS-Camel-wsdl">wsdl</a></li><li><a shape="rect"
href="#Tutorial-AXIS-Camel-ConfiguringAxis">Configuring Axis</a></li><li><a
shape="rect" href="#Tutorial-AXIS-Camel-RunningtheExample">Running the
Example</a></li></ul>
@@ -20072,11 +20072,11 @@ template.send("direct:alias-verify&
</div>
</div>
<p>The <strong>cxf:</strong> component provides integration with <a
shape="rect" href="http://cxf.apache.org";>Apache CXF</a> for connecting to
JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1408972751700 {padding: 0px;}
-div.rbtoc1408972751700 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1408972751700 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1409044682647 {padding: 0px;}
+div.rbtoc1409044682647 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1409044682647 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1408972751700">
+/*]]>*/</style></p><div class="toc-macro rbtoc1409044682647">
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF
Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI
format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#CXF-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
@@ -24013,84 +24013,30 @@ httpComponent.setHttpClientConfigurer(ne
]]></script>
</div></div><p>As long as you implement the HttpClientConfigurer and configure
your keystore and truststore as described above, it will work
fine.</p><p></p><h3 id="BookInOnePage-SeeAlso.42">See Also</h3>
<ul><li><a shape="rect" href="configuring-camel.html">Configuring
Camel</a></li><li><a shape="rect"
href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect"
href="getting-started.html">Getting Started</a></li></ul><ul
class="alternate"><li><a shape="rect" href="jetty.html">Jetty</a></li></ul>
-<h2 id="BookInOnePage-iBATIS">iBATIS</h2>
-
-<p>The <strong>ibatis:</strong> component allows you to query, poll, insert,
update and delete data in a relational database using <a shape="rect"
class="external-link" href="http://ibatis.apache.org/";>Apache iBATIS</a>.</p>
-
- <div class="aui-message problem shadowed information-macro">
+<h2 id="BookInOnePage-iBATIS">iBATIS</h2><p>The <strong>ibatis:</strong>
component allows you to query, poll, insert, update and delete data in a
relational database using <a shape="rect" class="external-link"
href="http://ibatis.apache.org/";>Apache iBATIS</a>.</p> <div
class="aui-message problem shadowed information-macro">
<p class="title">Prefer MyBatis</p>
<span class="aui-icon icon-problem">Icon</span>
<div class="message-content">
-
-<p>The Apache iBatis project is no longer active. The project is moved outside
Apache and is now know as the MyBatis project.<br clear="none">
-Therefore we encourage users to use <a shape="rect"
href="mybatis.html">MyBatis</a> instead. This camel-ibatis component will be
removed in Camel 3.0.</p>
+ <p>The Apache iBatis project is no longer active.
The project is moved outside Apache and is now know as the MyBatis project.<br
clear="none">Therefore we encourage users to use <a shape="rect"
href="mybatis.html">MyBatis</a> instead. This camel-ibatis component will be
removed in Camel 3.0.</p><p>iBatis do not support Spring 4.x. So you can only
use Spring 3.x or older with iBatis.</p>
</div>
</div>
-
-
-<p>Maven users will need to add the following dependency to their
<code>pom.xml</code> for this component:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<dependency>
+<p>Maven users will need to add the following dependency to their
<code>pom.xml</code> for this component:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-ibatis</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-URIformat.28">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-ibatis:statementName[?options]
+</div></div><h3 id="BookInOnePage-URIformat.28">URI format</h3><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[ibatis:statementName[?options]
]]></script>
-</div></div>
-
-<p>Where <strong>statementName</strong> is the name in the iBATIS XML
configuration file which maps to the query, insert, update or delete operation
you wish to evaluate.</p>
-
-<p>You can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p>
-
-<p>This component will by default load the iBatis SqlMapConfig file from the
root of the classpath and expected named as <code>SqlMapConfig.xml</code>.<br
clear="none">
-It uses Spring resource loading so you can define it using
<code>classpath</code>, <code>file</code> or <code>http</code> as prefix to
load resources with those schemes.<br clear="none">
-In Camel 2.2 you can configure this on the iBatisComponent with the
<code>setSqlMapConfig(String)</code> method.</p>
-
-<h3 id="BookInOnePage-Options.44">Options</h3>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Option </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>consumer.onConsume</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> 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.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>consumer.useIterator</code> </p></td><td colspan="1" rowspa
n="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> If <code>true</code> each row returned
when polling will be processed individually. If <code>false</code> the entire
<code>List</code> of data is set as the IN body. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>consumer.routeEmptyResultSet</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Sets whether empty result set
should be routed or not. By default, empty result sets are not routed.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>statementType</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>StatementType</code> </p></td><
td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Mandatory to
specify for IbatisProducer to control which iBatis <code>SqlMapClient</code>
method to invoke. The enum values are: <code>QueryForObject</code>,
<code>QueryForList</code>, <code>Insert</code>, <code>Update</code>,
<code>Delete</code>. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>maxMessagesPerPoll</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> 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.
</p></td></tr><tr><td colspan="1" rowspan="1" cl
ass="confluenceTd"><p> <code>isolation</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>TRANSACTION_REPEATABLE_READ</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.9:</strong> A String the defines the
transaction isolation level of the will be used. Allowed values are
TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED,
TRANSACTION_REPEATABLE_READ, TRANSACTION_SERIALIZABLE
</p></td></tr></tbody></table></div>
-
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>isolation</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>String</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>TRANSACTION_REPEATABLE_READ</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9:</strong> A
String the defines the transaction isolation level of the will be used. Allowed
values are TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED,
TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ,
TRANSACTION_SERIALIZABLE </p></td></tr></tbody></table></div>
-
-</div>
-
-<h3 id="BookInOnePage-MessageHeaders.7">Message Headers</h3>
-<p>Camel will populate the result message, either IN or OUT with a header with
the operationName used:</p>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Header </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>CamelIBatisStatementName</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> The <strong>statementName</strong> used
(for example: insertAccount). </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>CamelIBatisResult</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>Object</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The
<strong>response</strong> returned from iBatis in any of the operations. For
instance an <code>INSERT</code> could return the auto-generated key, or number o
f rows etc. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="BookInOnePage-MessageBody.2">Message Body</h3>
-<p>The response from iBatis will only be set as body if it's a
<code>SELECT</code> statement. That means, for example, for <code>INSERT</code>
statements Camel will not replace the body. This allows you to continue routing
and keep the original body. The response from iBatis is always stored in the
header with the key <code>CamelIBatisResult</code>.</p>
-
-<h3 id="BookInOnePage-Samples.12">Samples</h3>
-
-<p>For example if you wish to consume beans from a JMS queue and insert them
into a database you could do the following:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-from("activemq:queue:newAccount").
+</div></div><p>Where <strong>statementName</strong> is the name in the iBATIS
XML configuration file which maps to the query, insert, update or delete
operation you wish to evaluate.</p><p>You can append query options to the URI
in the following format,
<code>?option=value&option=value&...</code></p><p>This component will
by default load the iBatis SqlMapConfig file from the root of the classpath and
expected named as <code>SqlMapConfig.xml</code>.<br clear="none"> It uses
Spring resource loading so you can define it using <code>classpath</code>,
<code>file</code> or <code>http</code> as prefix to load resources with those
schemes.<br clear="none"> In Camel 2.2 you can configure this on the
iBatisComponent with the <code>setSqlMapConfig(String)</code> method.</p><h3
id="BookInOnePage-Options.44">Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Option</p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>consumer.onConsume</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>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.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>consumer.useIterator</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" r
owspan="1" class="confluenceTd"><p>If <code>true</code> each row returned when
polling will be processed individually. If <code>false</code> the entire
<code>List</code> of data is set as the IN body.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>consumer.routeEmptyResultSet</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Sets whether empty result set should be
routed or not. By default, empty result sets are not
routed.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>statementType</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>StatementType</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Mandatory to specify for
IbatisProducer to
control which iBatis <code>SqlMapClient</code> method to invoke. The enum
values are: <code>QueryForObject</code>, <code>QueryForList</code>,
<code>Insert</code>, <code>Update</code>,
<code>Delete</code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxMessagesPerPoll</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>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.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>isolation</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p
><code>TRANSACTION_REPEATABLE_READ</code></p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><strong>Camel 2.9:</strong> A String the defines the
>transaction isolation level of the will be used. Allowed values are
>TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED,
>TRANSACTION_REPEATABLE_READ,
>TRANSACTION_SERIALIZABLE</p></td></tr></tbody></table></div><div
>class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1"
>rowspan="1" class="confluenceTd"><p><code>isolation</code></p></td><td
>colspan="1" rowspan="1"
>class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
>rowspan="1"
>class="confluenceTd"><p><code>TRANSACTION_REPEATABLE_READ</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> A
>String the defines the transaction isolation level of the will be used.
>Allowed values are TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED,
>TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ, T
RANSACTION_SERIALIZABLE</p></td></tr></tbody></table></div></div><h3
id="BookInOnePage-MessageHeaders.7">Message Headers</h3><p>Camel will populate
the result message, either IN or OUT with a header with the operationName
used:</p><div class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Header</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>CamelIBatisStatementName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The
<strong>statementName</strong> used (for example:
insertAccount).</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>CamelIBatisResult</code></p></td><td colspan="1"
rowspan="1" class="confluence
Td"><p><code>Object</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>The <strong>response</strong> returned from iBatis in
any of the operations. For instance an <code>INSERT</code> could return the
auto-generated key, or number of rows
etc.</p></td></tr></tbody></table></div></div><h3
id="BookInOnePage-MessageBody.2">Message Body</h3><p>The response from iBatis
will only be set as body if it's a <code>SELECT</code> statement. That means,
for example, for <code>INSERT</code> statements Camel will not replace the
body. This allows you to continue routing and keep the original body. The
response from iBatis is always stored in the header with the key
<code>CamelIBatisResult</code>.</p><h3
id="BookInOnePage-Samples.12">Samples</h3><p>For example if you wish to consume
beans from a JMS queue and insert them into a database you could do the
following:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("activemq:queue:newAccount").
to("ibatis:insertAccount?statementType=Insert");
]]></script>
-</div></div>
-
-<p>Notice we have to specify the <code>statementType</code>, as we need to
instruct Camel which <code>SqlMapClient</code> operation to invoke.</p>
-
-<p>Where <strong>insertAccount</strong> is the iBatis ID in the SQL map
file:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
- <!-- Insert example, using the Account parameter class -->
+</div></div><p>Notice we have to specify the <code>statementType</code>, as we
need to instruct Camel which <code>SqlMapClient</code> operation to
invoke.</p><p>Where <strong>insertAccount</strong> is the iBatis ID in the SQL
map file:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[ <!-- Insert example, using the Account
parameter class -->
<insert id="insertAccount"
parameterClass="Account">
insert into ACCOUNT (
ACC_ID,
@@ -24103,88 +24049,51 @@ from("activemq:queue:newAccount&quo
)
</insert>
]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-UsingStatementTypeforbettercontrolofIBatis">Using
StatementType for better control of IBatis</h3>
-<p>When routing to an iBatis endpoint you want more fine grained control so
you can control whether the SQL statement to be executed is a
<code>SELEECT</code>, <code>UPDATE</code>, <code>DELETE</code> or
<code>INSERT</code> etc. So for instance if we want to route to an iBatis
endpoint in which the IN body contains parameters to a <code>SELECT</code>
statement we can do:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><h3
id="BookInOnePage-UsingStatementTypeforbettercontrolofIBatis">Using
StatementType for better control of IBatis</h3><p>When routing to an iBatis
endpoint you want more fine grained control so you can control whether the SQL
statement to be executed is a <code>SELEECT</code>, <code>UPDATE</code>,
<code>DELETE</code> or <code>INSERT</code> etc. So for instance if we want to
route to an iBatis endpoint in which the IN body contains parameters to a
<code>SELECT</code> statement we can do:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from("direct:start")
.to("ibatis:selectAccountById?statementType=QueryForObject")
.to("mock:result");
]]></script>
-</div></div>
-
-<p>In the code above we can invoke the iBatis statement
<code>selectAccountById</code> and the IN body should contain the account id we
want to retrieve, such as an <code>Integer</code> type.</p>
-
-<p>We can do the same for some of the other operations, such as
<code>QueryForList</code>:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>In the code above we can invoke the iBatis statement
<code>selectAccountById</code> and the IN body should contain the account id we
want to retrieve, such as an <code>Integer</code> type.</p><p>We can do the
same for some of the other operations, such as
<code>QueryForList</code>:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from("direct:start")
.to("ibatis:selectAllAccounts?statementType=QueryForList")
.to("mock:result");
]]></script>
-</div></div>
-
-<p>And the same for <code>UPDATE</code>, where we can send an
<code>Account</code> object as IN body to iBatis:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>And the same for <code>UPDATE</code>, where we can send an
<code>Account</code> object as IN body to iBatis:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from("direct:start")
.to("ibatis:updateAccount?statementType=Update")
.to("mock:result");
]]></script>
-</div></div>
-
-
-<h4 id="BookInOnePage-Scheduledpollingexample">Scheduled polling example</h4>
-<p>Since this component does not support scheduled polling, you need to use
another mechanism for triggering the scheduled polls, such as the <a
shape="rect" href="timer.html">Timer</a> or <a shape="rect"
href="quartz.html">Quartz</a> components.</p>
-
-<p>In the sample below we poll the database, every 30 seconds using the <a
shape="rect" href="timer.html">Timer</a> component and send the data to the JMS
queue:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-from("timer://pollTheDatabase?delay=30000").to("ibatis:selectAllAccounts?statementType=QueryForList").to("activemq:queue:allAccounts");
+</div></div><h4 id="BookInOnePage-Scheduledpollingexample">Scheduled polling
example</h4><p>Since this component does not support scheduled polling, you
need to use another mechanism for triggering the scheduled polls, such as the
<a shape="rect" href="timer.html">Timer</a> or <a shape="rect"
href="quartz.html">Quartz</a> components.</p><p>In the sample below we poll the
database, every 30 seconds using the <a shape="rect"
href="timer.html">Timer</a> component and send the data to the JMS
queue:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("timer://pollTheDatabase?delay=30000").to("ibatis:selectAllAccounts?statementType=QueryForList").to("activemq:queue:allAccounts");
]]></script>
-</div></div>
-
-<p>And the iBatis SQL map file used:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
- <!-- Select with no parameters using the result map for Account class.
-->
+</div></div><p>And the iBatis SQL map file used:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[ <!-- Select with no parameters using the
result map for Account class. -->
<select id="selectAllAccounts"
resultMap="AccountResult">
select * from ACCOUNT
</select>
]]></script>
-</div></div>
-
-<h4 id="BookInOnePage-UsingonConsume">Using onConsume</h4>
-<p>This component supports executing statements <strong>after</strong> data
have been consumed and processed by Camel. This allows you to do post updates
in the database. Notice all statements must be <code>UPDATE</code> statements.
Camel supports executing multiple statements whose name should be separated by
comma.</p>
-
-<p>The route below illustrates we execute the <strong>consumeAccount</strong>
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 pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><h4 id="BookInOnePage-UsingonConsume">Using onConsume</h4><p>This
component supports executing statements <strong>after</strong> data have been
consumed and processed by Camel. This allows you to do post updates in the
database. Notice all statements must be <code>UPDATE</code> statements. Camel
supports executing multiple statements whose name should be separated by
comma.</p><p>The route below illustrates we execute the
<strong>consumeAccount</strong> 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 pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from("ibatis:selectUnprocessedAccounts?consumer.onConsume=consumeAccount").to("mock:results");
]]></script>
-</div></div>
-
-<p>And the statements in the sqlmap file:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>And the statements in the sqlmap file:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
<select id="selectUnprocessedAccounts"
resultMap="AccountResult">
select * from ACCOUNT where PROCESSED = false
</select>
]]></script>
-</div></div>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
<update id="consumeAccount" parameterClass="Account">
update ACCOUNT set PROCESSED = true where ACC_ID = #id#
</update>
]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-SeeAlso.43">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring
Camel</a></li><li><a shape="rect"
href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect"
href="getting-started.html">Getting Started</a></li></ul>
-<ul class="alternate"><li><a shape="rect"
href="mybatis.html">MyBatis</a></li></ul>
+</div></div><p></p><h3 id="BookInOnePage-SeeAlso.43">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring
Camel</a></li><li><a shape="rect"
href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect"
href="getting-started.html">Getting Started</a></li></ul><ul
class="alternate"><li><a shape="rect" href="mybatis.html">MyBatis</a></li></ul>
<h2 id="BookInOnePage-IRCComponent">IRC Component</h2>
<p>The <strong>irc</strong> component implements an <a shape="rect"
class="external-link" href="http://en.wikipedia.org/wiki/Internet_Relay_Chat";
rel="nofollow">IRC</a> (Internet Relay Chat) transport.</p>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
