Author: buildbot
Date: Tue May 6 15:17:59 2014
New Revision: 908193
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/jdbc.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/jdbc.html
==============================================================================
--- websites/production/camel/content/jdbc.html (original)
+++ websites/production/camel/content/jdbc.html Tue May 6 15:17:59 2014
@@ -86,136 +86,56 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="JDBC-JDBCComponent">JDBC
Component</h2>
-
-<p>The <strong>jdbc</strong> component enables you to access databases through
JDBC, where SQL queries and operations are sent in the message body. This
component uses the standard JDBC API, unlike the <a shape="rect"
href="sql-component.html">SQL Component</a> component, which uses
spring-jdbc.</p>
-
-<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: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<dependency>
+<div class="wiki-content maincontent"><h2 id="JDBC-JDBCComponent">JDBC
Component</h2><p>The <strong>jdbc</strong> component enables you to access
databases through JDBC, where SQL queries and operations are sent in the
message body. This component uses the standard JDBC API, unlike the <a
shape="rect" href="sql-component.html">SQL Component</a> component, which uses
spring-jdbc.</p><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: java; gutter: false"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-jdbc</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
]]></script>
-</div></div>
-
- <div class="aui-message problem shadowed information-macro">
+</div></div> <div class="aui-message problem shadowed information-macro">
<span class="aui-icon icon-problem">Icon</span>
<div class="message-content">
-
-<p>This component can only be used to define producer endpoints, which means
that you cannot use the JDBC component in a <code>from()</code> statement.</p>
+ <p>This component can only be used to define
producer endpoints, which means that you cannot use the JDBC component in a
<code>from()</code> statement.</p>
</div>
</div>
-
-
- <div class="aui-message hint shadowed information-macro">
- <span class="aui-icon icon-hint">Icon</span>
- <div class="message-content">
-
-<p>This component can not be used as a <a shape="rect" class="external-link"
href="http://camel.apache.org/transactional-client.html";>Transactional
Client</a>. If you need transaction support in your route, you should use the
<a shape="rect" class="external-link"
href="http://camel.apache.org/sql-component.html";>SQL component</a> instead.</p>
- </div>
- </div>
-
-
-<h3 id="JDBC-URIformat">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[
-jdbc:dataSourceName[?options]
+<h3 id="JDBC-URIformat">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[jdbc:dataSourceName[?options]
]]></script>
-</div></div>
-
-<p>This component only supports producer endpoints.</p>
-
-<p>You can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p>
-
-<h3 id="JDBC-Options">Options</h3>
-
-<div class="confluenceTableSmall">
+</div></div><p>This component only supports producer endpoints.</p><p>You can
append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="JDBC-Options">Options</h3><div class="confluenceTableSmall">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>readSize</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> The default maximum number of
rows that can be read by a polling query. The default value is 0.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>statement.<xxx></code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.1:</strong> Sets additional options on
the <code>java.sql.Statement</code> that is used behind the scenes to execute
the queries. For instance, <code>state
ment.maxRows=10</code>. For detailed documentation, see the <a shape="rect"
class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Statement.html";
rel="nofollow"><code>java.sql.Statement</code> javadoc</a> documentation.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>useJDBC4ColumnNameAndLabelSemantics</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.2:</strong> Sets whether
to use JDBC 4/3 column label/name semantics. You can use this option to turn it
<code>false</code> in case you have issues with your JDBC driver to select
data. This only applies when using <code>SQL SELECT</code> using aliases (e.g.
<code>SQL SELECT id as identifier, name as given_name from persons</code>).
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>resetAutoCommit</code> </p></td><td colspan="1" rowspan="1" clas
s="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.9:</strong> Camel will set the
autoCommit on the JDBC connection to be false, commit the change after executed
the statement and reset the autoCommit flag of the connection at the end, if
the resetAutoCommit is true. If the JDBC connection doesn't support to reset
the autoCommit flag, you can set the resetAutoCommit flag to be false, and
Camel will not try to reset the autoCommit flag.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>allowNamedParameters</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.12:</strong> Whether to allow using
named parameters in the queries. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>prepareStatementStrategy</code> </p></td><td
colspan="1" rowspan="1" class="conflue
nceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<strong>Camel 2.12:</strong> Allows to plugin to use a custom
<code>org.apache.camel.component.jdbc.JdbcPrepareStatementStrategy</code> to
control preparation of the query and prepared statement. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>useHeadersAsParameters</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12:</strong> Set this
option to <code>true</code> to use the <code>prepareStatementStrategy</code>
with named parameters. This allows to define queries with named placeholders,
and use headers with the dynamic values for the query placeholders.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>outputType</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>SelectList</code> </p></td><td colspan="1" rowspa
n="1" class="confluenceTd"><p> <strong>Camel 2.12.1:</strong> Make the output
of the producer to SelectList as List of Map, or SelectOne as single Java
object in the following way:<br clear="none">
a) If the query has only single column, then that JDBC Column object is
returned. (such as SELECT COUNT( * ) FROM PROJECT will return a Long object.<br
clear="none">
b) If the query has more than one column, then it will return a Map of that
result.<br clear="none">
c) If the outputClass is set, then it will convert the query result into an
Java bean object by calling all the setters that match the column names. It
will assume your class has a default constructor to create instance with.<br
clear="none">
d) If the query resulted in more than one rows, it throws an non-unique result
exception.</p></td></tr><tr><td></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>outputClass</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12.1:</strong> Specify the
full package and class name to use as conversion when outputType=SelectOne.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>beanRowMapper</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.12.1:</strong> To use a custom
<code>org.apache.camel.component.jdbc.BeanRowMapper</code> when using
<code>outputClass</code>. The default implementation will lower case the row
names and skip underscores, and dashes. For example <code>"CUST_ID"</code> is
mapped as <code>"custId"</code>. <
/p></td></tr></tbody></table>
-</div>
-
-<h3 id="JDBC-Result">Result</h3>
-<p>By default the result is returned in the OUT body as an
<code>ArrayList<HashMap<String, Object>></code>. The
<code>List</code> object contains the list of rows and the <code>Map</code>
objects contain each row with the <code>String</code> key as the column name.
You can use the option <code>outputType</code> to control the result.</p>
-
-<p><strong>Note:</strong> This component fetches
<code>ResultSetMetaData</code> to be able to return the column name as the key
in the <code>Map</code>.</p>
-
-<h4 id="JDBC-MessageHeaders">Message Headers</h4>
-<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> Description
</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>CamelJdbcRowCount</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> If the query is a <code>SELECT</code>, query the row
count is returned in this OUT header. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>CamelJdbcUpdateCount</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If the query is
an <code>UPDATE</code>, query the update count is returned in this OUT header.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>CamelGeneratedKeysRows</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.10:</strong> Rows that contains the
generated kets. </p></td></tr><tr><td colspan="1" rowspan="
1" class="confluenceTd"><p> <code>CamelGeneratedKeysRowCount</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.10:</strong> The number of rows in the header that contains generated keys.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>CamelJdbcColumnNames</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.11.1:</strong> The column names from
the ResultSet as a <code>java.util.Set</code> type. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>CamelJdbcParametes</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.12:</strong> A
<code>java.util.Map</code> which has the headers to be used if
<code>useHeadersAsParameters</code> has been enabled.
</p></td></tr></tbody></table></div>
-
-
-<h3 id="JDBC-Generatedkeys">Generated keys</h3>
-<p><strong>Available as of Camel 2.10</strong></p>
-
-<p>If you insert data using SQL INSERT, then the RDBMS may support auto
generated keys. You can instruct the <a shape="rect" href="jdbc.html">JDBC</a>
producer to return the generated keys in headers.<br clear="none">
-To do that set the header <code>CamelRetrieveGeneratedKeys=true</code>. Then
the generated keys will be provided as headers with the keys listed in the
table above.</p>
-
-<p>You can see more details in this <a shape="rect" class="external-link"
href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-jdbc/src/test/java/org/apache/camel/component/jdbc/JdbcGeneratedKeysTest.java";>unit
test</a>.</p>
-
- <div class="aui-message hint shadowed information-macro">
+</div><h3 id="JDBC-Result">Result</h3><p>By default the result is returned in
the OUT body as an <code>ArrayList<HashMap<String, Object>></code>.
The <code>List</code> object contains the list of rows and the <code>Map</code>
objects contain each row with the <code>String</code> key as the column name.
You can use the option <code>outputType</code> to control the
result.</p><p><strong>Note:</strong> This component fetches
<code>ResultSetMetaData</code> to be able to return the column name as the key
in the <code>Map</code>.</p><h4 id="JDBC-MessageHeaders">Message
Headers</h4><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>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>CamelJdbcRowCount</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>If the query is a
<code>SELECT</code>, query t
he row count is returned in this OUT header.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>CamelJdbcUpdateCount</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>If the query is an
<code>UPDATE</code>, query the update count is returned in this OUT
header.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>CamelGeneratedKeysRows</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong>
Rows that contains the generated kets.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>CamelGeneratedKeysRowCount</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong>
The number of rows in the header that contains generated
keys.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>CamelJdbcColumnNames</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11.1:</strong>
The co
lumn names from the ResultSet as a <code>java.util.Set</code>
type.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>CamelJdbcParametes</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong> A
<code>java.util.Map</code> which has the headers to be used if
<code>useHeadersAsParameters</code> has been
enabled.</p></td></tr></tbody></table></div><h3
id="JDBC-Generatedkeys">Generated keys</h3><p><strong>Available as of Camel
2.10</strong></p><p>If you insert data using SQL INSERT, then the RDBMS may
support auto generated keys. You can instruct the <a shape="rect"
href="jdbc.html">JDBC</a> producer to return the generated keys in headers.<br
clear="none"> To do that set the header
<code>CamelRetrieveGeneratedKeys=true</code>. Then the generated keys will be
provided as headers with the keys listed in the table above.</p><p>You can see
more details in this <a shape="rect" class="external-link"
href="https://svn.apache.org
/repos/asf/camel/trunk/components/camel-jdbc/src/test/java/org/apache/camel/component/jdbc/JdbcGeneratedKeysTest.java">unit
test</a>.</p> <div class="aui-message hint shadowed information-macro">
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
-
-<p>Using generated keys does not work with together with named parameters.</p>
+ <p>Using generated keys does not work with
together with named parameters.</p>
</div>
</div>
-
-
-
-<h3 id="JDBC-Usingnamedparameters">Using named parameters</h3>
-<p><strong>Available as of Camel 2.12</strong></p>
-
-<p>In the given route below, we want to get all the projects from the projects
table. Notice the SQL query has 2 named parameters, :?lic and :?min.<br
clear="none">
-Camel will then lookup these parameters from the message headers. Notice in
the example above we set two headers with constant value<br clear="none">
-for the named parameters:</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:projects")
+<h3 id="JDBC-Usingnamedparameters">Using named
parameters</h3><p><strong>Available as of Camel 2.12</strong></p><p>In the
given route below, we want to get all the projects from the projects table.
Notice the SQL query has 2 named parameters, :?lic and :?min.<br clear="none">
Camel will then lookup these parameters from the message headers. Notice in the
example above we set two headers with constant value<br clear="none"> for the
named parameters:</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:projects")
.setHeader("lic", constant("ASF"))
.setHeader("min", constant(123))
.setBody("select * from projects where license = :?lic and id >
:?min order by id")
.to("jdbc:myDataSource?useHeadersAsParameters=true")
]]></script>
-</div></div>
-
-<p>You can also store the header values in a <code>java.util.Map</code> and
store the map on the headers with the key <code>CamelJdbcParameters</code>.</p>
-
-
-<h3 id="JDBC-Samples">Samples</h3>
-
-<p>In the following example, we fetch the rows from the customer table.</p>
-
-<p>First we register our datasource in the Camel registry as
<code>testdb</code>:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>You can also store the header values in a
<code>java.util.Map</code> and store the map on the headers with the key
<code>CamelJdbcParameters</code>.</p><h3 id="JDBC-Samples">Samples</h3><p>In
the following example, we fetch the rows from the customer table.</p><p>First
we register our datasource in the Camel registry as
<code>testdb</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[
JndiRegistry reg = super.createRegistry();
reg.bind("testdb", db);
return reg;
]]></script>
-</div></div>
-
-<p>Then we configure a route that routes to the JDBC component, so the SQL
will be executed. Note how we refer to the <code>testdb</code> datasource that
was bound in the previous step:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>Then we configure a route that routes to the JDBC component, so
the SQL will be executed. Note how we refer to the <code>testdb</code>
datasource that was bound in the previous step:</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[
// lets add simple route
public void configure() throws Exception {
from("direct:hello").to("jdbc:testdb?readSize=100");
}
]]></script>
-</div></div>
-
-<p>Or you can create a <code>DataSource</code> in Spring like this:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>Or you can create a <code>DataSource</code> in Spring like
this:</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[
<camelContext id="camel"
xmlns="http://camel.apache.org/schema/spring">
<route>
@@ -234,11 +154,7 @@ public void configure() throws Exception
<jdbc:script location="classpath:sql/init.sql"/>
</jdbc:embedded-database>
]]></script>
-</div></div>
-
-<p>We create an endpoint, add the SQL query to the body of the IN message, and
then send the exchange. The result of the query is returned in the OUT body:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>We create an endpoint, add the SQL query to the body of the IN
message, and then send the exchange. The result of the query is returned in the
OUT body:</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[
// first we create our exchange using the endpoint
Endpoint endpoint = context.getEndpoint("direct:hello");
@@ -262,11 +178,7 @@ row = data.get(1);
assertEquals("cust2", row.get("ID"));
assertEquals("nsandhu", row.get("NAME"));
]]></script>
-</div></div>
-
-<p>If you want to work on the rows one by one instead of the entire ResultSet
at once you need to use the <a shape="rect" href="splitter.html">Splitter</a>
EIP such as:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>If you want to work on the rows one by one instead of the
entire ResultSet at once you need to use the <a shape="rect"
href="splitter.html">Splitter</a> EIP such as:</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:hello")
// here we split the data from the testdb into new messages one by one
@@ -274,21 +186,11 @@ from("direct:hello")
.to("jdbc:testdb").split(body()).to("mock:result");
]]></script>
-</div></div>
-
-<h3 id="JDBC-Sample-Pollingthedatabaseeveryminute">Sample - Polling the
database every minute</h3>
-<p>If we want to poll a database using the JDBC component, we need to combine
it with a polling scheduler such as the <a shape="rect"
href="timer.html">Timer</a> or <a shape="rect" href="quartz.html">Quartz</a>
etc. In the following example, we retrieve data from the database every 60
seconds:</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://foo?period=60000").setBody(constant("select *
from
customer")).to("jdbc:testdb").to("activemq:queue:customers");
+</div></div><h3 id="JDBC-Sample-Pollingthedatabaseeveryminute">Sample -
Polling the database every minute</h3><p>If we want to poll a database using
the JDBC component, we need to combine it with a polling scheduler such as the
<a shape="rect" href="timer.html">Timer</a> or <a shape="rect"
href="quartz.html">Quartz</a> etc. In the following example, we retrieve data
from the database every 60 seconds:</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://foo?period=60000").setBody(constant("select
* from
customer")).to("jdbc:testdb").to("activemq:queue:customers");
]]></script>
-</div></div>
-
-
-<h3 id="JDBC-SeeAlso">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="sql.html">SQL</a></li></ul></div>
+</div></div><p></p><h3 id="JDBC-SeeAlso">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="sql.html">SQL</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
