Author: buildbot
Date: Tue Mar 15 20:23:00 2016
New Revision: 982883
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
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 Mar 15
20:23:00 2016
@@ -1016,11 +1016,11 @@ template.send("direct:alias-verify&
]]></script>
</div></div><p></p><h3 id="BookComponentAppendix-SeeAlso.8">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><li><a
shape="rect" href="crypto.html">Crypto</a> Crypto is also available as a <a
shape="rect" href="data-format.html">Data Format</a></li></ul> <h2
id="BookComponentAppendix-CXFComponent">CXF Component</h2><div
class="confluence-information-macro confluence-information-macro-note"><span
class="aui-icon aui-icon-small aui-iconfont-warning
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When using CXF as a consumer, the
<a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows
you to factor out how message payloads are received from their processing as a
RESTful or SOAP web service. This has the potential of using a multitude of
transports to cons
ume web services. The bean component's configuration is also simpler and
provides the fastest method to implement web services using Camel and
CXF.</p></div></div><div class="confluence-information-macro
confluence-information-macro-tip"><span class="aui-icon aui-icon-small
aui-iconfont-approve confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When using CXF in streaming modes
(see DataFormat option), then also read about <a shape="rect"
href="stream-caching.html">Stream caching</a>.</p></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.rbtoc1457961475655 {padding: 0px;}
-div.rbtoc1457961475655 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1457961475655 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1458073132389 {padding: 0px;}
+div.rbtoc1458073132389 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1458073132389 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1457961475655">
+/*]]>*/</style></p><div class="toc-macro rbtoc1458073132389">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookComponentAppendix-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookComponentAppendix-URIformat">URI format</a></li><li><a shape="rect"
href="#BookComponentAppendix-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookComponentAppendix-Thedescriptionsofthedataformats">The descriptions
of the dataformats</a>
@@ -1884,69 +1884,23 @@ queryMap.put("q1", "new&q
queryMap.put("q2", "world");
inMessage.setHeader(CxfConstants.CAMEL_CXF_RS_QUERY_MAP, queryMap);
]]></script>
-</div></div> <h2 id="BookComponentAppendix-DataSetComponent">DataSet
Component</h2>
-
-<a shape="rect" href="testing.html">Testing</a> of distributed and
asynchronous processing is notoriously difficult. The <a shape="rect"
href="mock.html">Mock</a>, <a shape="rect" href="test.html">Test</a> and <a
shape="rect" href="dataset.html">DataSet</a> endpoints work great with the <a
shape="rect" href="testing.html">Camel Testing Framework</a> to simplify your
unit and integration testing using <a shape="rect"
href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a>
and Camel's large range of <a shape="rect"
href="components.html">Components</a> together with the powerful <a
shape="rect" href="bean-integration.html">Bean Integration</a>.
-
-<p>The DataSet component provides a mechanism to easily perform load &
soak testing of your system. It works by allowing you to create <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/dataset/DataSet.html";>DataSet
instances</a> both as a source of messages and as a way to assert that the
data set is received.</p>
-
-<p>Camel will use the <a shape="rect" href="log.html">throughput logger</a>
when sending dataset's. </p>
-
-<h3 id="BookComponentAppendix-URIformat.13">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
-dataset:name[?options]
+</div></div> <h2 id="BookComponentAppendix-DataSetComponent">DataSet
Component</h2><p><a shape="rect" href="testing.html">Testing</a> of distributed
and asynchronous processing is notoriously difficult. The <a shape="rect"
href="mock.html">Mock</a>, <a shape="rect" href="test.html">Test</a> and <a
shape="rect" href="dataset.html">DataSet</a> endpoints work great with the <a
shape="rect" href="testing.html">Camel Testing Framework</a> to simplify your
unit and integration testing using <a shape="rect"
href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a>
and Camel's large range of <a shape="rect"
href="components.html">Components</a> together with the powerful <a
shape="rect" href="bean-integration.html">Bean Integration</a>.</p><p>The
DataSet component provides a mechanism to easily perform load & soak
testing of your system. It works by allowing you to create <a shape="rect"
class="external-link" href="http://camel.apache.org/maven/current/camel-core/a
pidocs/org/apache/camel/component/dataset/DataSet.html">DataSet instances</a>
both as a source of messages and as a way to assert that the data set is
received.</p><p>Camel will use the <a shape="rect" href="log.html">throughput
logger</a> when sending dataset's.</p><h3
id="BookComponentAppendix-URIformat.13">URI format</h3><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[dataset:name[?options]
]]></script>
-</div></div>
-
-<p>Where <strong>name</strong> is used to find the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/dataset/DataSet.html";>DataSet
instance</a> in the <a shape="rect" href="registry.html">Registry</a></p>
-
-<p>Camel ships with a support implementation of
<code>org.apache.camel.component.dataset.DataSet</code>, the
<code>org.apache.camel.component.dataset.DataSetSupport</code> class, that can
be used as a base for implementing your own DataSet. Camel also ships with a
default implementation, the
<code>org.apache.camel.component.dataset.SimpleDataSet</code> that can be used
for testing.</p>
-
-<h3 id="BookComponentAppendix-Options.10">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> 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>produceDelay</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> 3 </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Allows a delay in ms to be specified, which causes
producers to pause in order to simulate slow producers. Uses a minimum of 3 ms
delay unless you set this option to -1 to force no delay at all.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>consumeDelay</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Allows a delay in ms to be specified, which causes
consumers to pause in order to simu
late slow consumers. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>preloadSize</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Sets how many messages should be preloaded (sent)
before the route completes its initialization. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>initialDelay</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000 </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.1:</strong>
Time period in millis to wait before starting sending messages.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>minRate</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Wait until the DataSet contains at least this number
of messages </p></td></tr></tbody></table></div>
-</div>
-
-<p>You can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p>
-
-<h3 id="BookComponentAppendix-ConfiguringDataSet">Configuring DataSet</h3>
-<p>Camel will lookup in the <a shape="rect" href="registry.html">Registry</a>
for a bean implementing the DataSet interface. So you can register your own
DataSet as:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
- <bean id="myDataSet"
class="com.mycompany.MyDataSet">
+</div></div><p>Where <strong>name</strong> is used to find the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/dataset/DataSet.html";>DataSet
instance</a> in the <a shape="rect"
href="registry.html">Registry</a></p><p>Camel ships with a support
implementation of <code>org.apache.camel.component.dataset.DataSet</code>, the
<code>org.apache.camel.component.dataset.DataSetSupport</code> class, that can
be used as a base for implementing your own DataSet. Camel also ships with some
implementations that can be used for testing:
 <code>org.apache.camel.component.dataset.SimpleDataSet</code>, <code><span>org.apache.camel.component.dataset.ListDataSet</span></code><span>
and </span><code><span><span>org.apache.camel.component.dataset.FileDataSet</span></span></code><span><span>,
all of which extend <code>DataSetSupport</code>.</span></span></p><h3
id="BookComponentAppendix-Options.10">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>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>produceDelay</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>3</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Allows a delay in ms to be specified, which
causes producers to pause in order to simulate slow producers. Uses a minimum
of 3 ms delay unless you set this option to -1 to force no delay at
all.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>consumeDelay</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Allows a delay in ms to be specified, which causes
consumers to pause
in order to simulate slow consumers.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>preloadSize</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Sets how many messages should be preloaded
(sent) before the route completes its initialization.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>initialDelay</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>1000</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.1:</strong> Time period in millis to
wait before starting sending messages.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>minRate</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Wait until the DataSet contains at least
this number of messages</p></td></tr><tr><td colspan="1" rowspan="1"
class="conflu
enceTd"><code>dataSetIndex</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><code>lenient</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.17:</strong> Controls the behavior of
the <em>CamelDataSetIndex</em> header. The supported values are
<code>strict</code>, <code>lenient</code> and <code>off</code>. The default
behavior prior to <strong>Camel 2.17</strong> can be restored using
<code><span>dataSetIndex</span>=strict</code></p><p>For consumers:<br
clear="none"> - <code>strict</code> or <code>lenient</code> => The
<em>CamelDataSetIndex</em> header will always be set<br clear="none"> -
<code>off</code> => The <em>CamelDataSetIndex</em> header will not be
set</p><p>For producers:<br clear="none"> - <code>strict</code> => The
<em>CamelDataSetIndex</em> header must be present and the value of the header
will be verified<br clear="none"> - <code>lenient</code> => If the
<em>CamelDataSetIndex</em> header is present, the value of the h
eader will be verified. If the header is not present, it will be set.<br
clear="none"> - <code>off</code> => If the <em>CamelDataSetIndex</em>
header is present, the value of the header will not be verified. If the header
is not present, it will not be
set.</p></td></tr></tbody></table></div></div><p>You can append query options
to the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="BookComponentAppendix-ConfiguringDataSet">Configuring DataSet</h3><p>Camel
will lookup in the <a shape="rect" href="registry.html">Registry</a> for a bean
implementing the DataSet interface. So you can register your own DataSet
as:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="myDataSet"
class="com.mycompany.MyDataSet">
<property name="size" value="100"/>
</bean>
]]></script>
-</div></div>
-
-<h3 id="BookComponentAppendix-Example.1">Example</h3>
-
-<p>For example, to test that a set of messages are sent to a queue and then
consumed from the queue without losing any messages:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
-// send the dataset to a queue
+</div></div><h3 id="BookComponentAppendix-Example.1">Example</h3><p>For
example, to test that a set of messages are sent to a queue and then consumed
from the queue without losing any messages:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[// send the dataset to a queue
from("dataset:foo").to("activemq:SomeQueue");
// now lets test that the messages are consumed correctly
from("activemq:SomeQueue").to("dataset:foo");
]]></script>
-</div></div>
-
-<p>The above would look in the <a shape="rect"
href="registry.html">Registry</a> to find the <strong>foo</strong> DataSet
instance which is used to create the messages.</p>
-
-<p>Then you create a DataSet implementation, such as using the
<code>SimpleDataSet</code> as described below, configuring things like how big
the data set is and what the messages look like etc.</p>
-
-<h3 id="BookComponentAppendix-PropertiesonSimpleDataSet">Properties on
SimpleDataSet</h3>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p>Property</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>defaultBody</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>Object</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code><hello>world!</hello></code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Specifies the default message body. For
SimpleDataSet it is a constant payload; though if you want to create custom
payloads per message, create your own derivation of
<code>DataSetSupport</code>. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>reportCount</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>long</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>-1</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the number of
messages to be received before reporting progress. Useful for showing progress
of a large load test. If < 0, then <code>size</code> / 5, if is 0 then
<code>size</code>, else set to <code>reportCount</code>
value.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>size</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>long</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>10</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Specifies how many messages to
send/consume.</p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="BookComponentAppendix-SeeAlso.10">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><li><a shape="rect" href="spring-testing.html">Spring
Testing</a></li></ul> <h2 id="BookComponentAppendix-Db4oComponent">Db4o
Component</h2>
+</div></div><p>The above would look in the <a shape="rect"
href="registry.html">Registry</a> to find the <strong>foo</strong> DataSet
instance which is used to create the messages.</p><p>Then you create a DataSet
implementation, such as using the <code>SimpleDataSet</code> as described
below, configuring things like how big the data set is and what the messages
look like etc.  </p><p> </p><h2
id="BookComponentAppendix-DataSetSupport(abstractclass)"><code>DataSetSupport</code> (abstract
class)</h2><p>The DataSetSupport abstract class is a nice starting point for
new DataSets, and provides some useful features to derived classes.</p><h3
id="BookComponentAppendix-PropertiesonDataSetSupport">Properties on
DataSetSupport</h3><div class="confluenceTableSmall"><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Property</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" ro
wspan="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>defaultHeaders</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>Map<String,Object></code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the default message
body. For SimpleDataSet it is a constant payload; though if you want to create
custom payloads per message, create your own derivation of
<code>DataSetSupport</code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>outputTransformer</code></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Processor</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span style="font-family:
monospace;">null</span></p></td><td colspan="1" rowspan="1" class="
confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>size</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>long</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>10</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Specifies how many messages to
send/consume.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>reportCount</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><code>long</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><code>-1</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><span>Specifies the number of messages to be received
before reporting progress. Useful for showing progress of a large load test. If
< 0, then </span><code>size</code><span> / 5, if is 0 then
</span><code>size</code><span>, else set to
</span><code>reportCount</code><span>
value.</span></td></tr></tbody></table></div></div><h3 id="BookCo
mponentAppendix-SimpleDataSet"><code>SimpleDataSet</code></h3><p>The
<code>SimpleDataSet</code> extends <code>DataSetSupport</code>, and adds a
default body.</p><h3
id="BookComponentAppendix-AdditionalPropertiesonSimpleDataSet">Additional
Properties on SimpleDataSet</h3><div class="confluenceTableSmall"><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Property</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>defaultBody</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>Object</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code><hello>world!</hello></code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the defau
lt message body. By default, the <code>SimpleDataSet</code> produces the same
constant payload for each exchange. If you want to customize the payload for
each exchange, create a Camel <code>Processor</code> and configure the
<code>SimpleDataSet</code> to use it by setting the
<code>outputTransformer</code>
property.</p></td></tr></tbody></table></div></div><h3
id="BookComponentAppendix-ListDataSet(Camel2.17)"><code>ListDataSet (Camel
2.17)</code></h3><p>The
List<code>DataSet</code> extends <code>DataSetSupport</code>, and
adds a list of default bodies.</p><h3
id="BookComponentAppendix-AdditionalPropertiesonListDataSet">Additional
Properties on ListDataSet</h3><div class="confluenceTableSmall"><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Property</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>defaultBodies</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>List<Object></code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>empty
LinkedList<Object></code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Specifies the default message body. By default, the
<code>ListDataSet</code><span> selects a constant payload from the list of
<code>defaultBodies</code> using the <code>CamelDataSetIndex</code>. If you
want to customize the payload, create a Camel </span><code>Processor</code> and
configure the <code>ListDataSet</code><span> to use it by setting the
</span><code>outputTransformer</code><span>
property.</span></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>size</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>long</code></p></td><td colspa
n="1" rowspan="1" class="confluenceTd"><p>the size of the defaultBodies
list</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>Specifies how many messages to send/consume. This
value can be different from the size of the <code>defaultBodies</code> list. If
the value is less than the size of the <code>defaultBodies</code> list, some of
the list elements will not be used. If the value is greater than the size of
the <code>defaultBodies</code> list, the payload for the exchange will be
selected using the modulus of the <code>CamelDataSetIndex</code> and the size
of the <code>defaultBodies</code> list (i.e. <code>CamelDataSetIndex %
defaultBodies.size()</code>
)</span></p></td></tr></tbody></table></div></div><h3
id="BookComponentAppendix-FileDataSet(Camel2.17)"><code>FileDataSet (Camel
2.17)</code></h3><p>The <code>SimpleDataSet</code> extends
<code>ListDataSet</code>, and adds support for loading the bodies from a
file.</p><h3 id="BookComponentAppendix-Additi
onalPropertiesonFileDataSet">Additional Properties on FileDataSet</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Property</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>sourceFile</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>File</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span style="font-family:
monospace;">null</span></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Specifies the source file for
payloads</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>delimiter</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><
td colspan="1" rowspan="1" class="confluenceTd"><p><span style="font-family:
monospace;">\z</span></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Specifies the delimiter pattern used by a
<code>java.util.Scanner</code> to split the file into multiple
payloads.</p></td></tr></tbody></table></div></div><p></p><h3
id="BookComponentAppendix-SeeAlso.10">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><li><a
shape="rect" href="spring-testing.html">Spring Testing</a></li></ul> <h2
id="BookComponentAppendix-Db4oComponent">Db4o Component</h2>
<p><strong>Available as of Camel 2.5</strong></p>
<p>The <strong>db4o:</strong> component allows you to work with <a
shape="rect" class="external-link" href="http://www.db4o.com";
rel="nofollow">db4o</a> NoSQL database. The camel-db4o library is provided by
the <a shape="rect" class="external-link"
href="http://code.google.com/p/camel-extra/"; rel="nofollow">Camel Extra</a>
project which hosts all *GPL related components for Camel.</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 Mar 15 20:23:00
2016
@@ -3741,11 +3741,11 @@ The tutorial has been designed in two pa
While not actual tutorials you might find working through the source of the
various <a shape="rect" href="examples.html">Examples</a> useful.</li></ul>
<h2 id="BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring
Remoting with JMS</h2><p> </p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Thanks</p><span
class="aui-icon aui-icon-small aui-iconfont-info
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>This tutorial was kindly donated
to Apache Camel by Martin Gilday.</p></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.rbtoc1457961489513 {padding: 0px;}
-div.rbtoc1457961489513 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1457961489513 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1458073205437 {padding: 0px;}
+div.rbtoc1458073205437 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1458073205437 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1457961489513">
+/*]]>*/</style></p><div class="toc-macro rbtoc1458073205437">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring
Remoting with JMS</a></li><li><a shape="rect"
href="#BookInOnePage-Preface">Preface</a></li><li><a shape="rect"
href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect"
href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect"
href="#BookInOnePage-About">About</a></li><li><a shape="rect"
href="#BookInOnePage-CreatetheCamelProject">Create the Camel Project</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-UpdatethePOMwithDependencies">Update the POM with
Dependencies</a></li></ul>
</li><li><a shape="rect" href="#BookInOnePage-WritingtheServer">Writing the
Server</a>
@@ -5860,11 +5860,11 @@ So we completed the last piece in the pi
<p>This example has been removed from <strong>Camel 2.9</strong> onwards.
Apache Axis 1.4 is a very old and unsupported framework. We encourage users to
use <a shape="rect" href="cxf.html">CXF</a> instead of Axis.</p></div></div>
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1457961490758 {padding: 0px;}
-div.rbtoc1457961490758 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1457961490758 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1458073206245 {padding: 0px;}
+div.rbtoc1458073206245 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1458073206245 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1457961490758">
+/*]]>*/</style><div class="toc-macro rbtoc1458073206245">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis
1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect"
href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect"
href="#BookInOnePage-Introduction">Introduction</a></li><li><a shape="rect"
href="#BookInOnePage-SettinguptheprojecttorunAxis">Setting up the project to
run Axis</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Maven2">Maven 2</a></li><li><a shape="rect"
href="#BookInOnePage-wsdl">wsdl</a></li><li><a shape="rect"
href="#BookInOnePage-ConfiguringAxis">Configuring Axis</a></li><li><a
shape="rect" href="#BookInOnePage-RunningtheExample">Running the
Example</a></li></ul>
@@ -17285,11 +17285,11 @@ template.send("direct:alias-verify&
]]></script>
</div></div><p></p><h3 id="BookInOnePage-SeeAlso.28">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><li><a
shape="rect" href="crypto.html">Crypto</a> Crypto is also available as a <a
shape="rect" href="data-format.html">Data Format</a></li></ul> <h2
id="BookInOnePage-CXFComponent">CXF Component</h2><div
class="confluence-information-macro confluence-information-macro-note"><span
class="aui-icon aui-icon-small aui-iconfont-warning
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When using CXF as a consumer, the
<a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows
you to factor out how message payloads are received from their processing as a
RESTful or SOAP web service. This has the potential of using a multitude of
transports to consume web
services. The bean component's configuration is also simpler and provides the
fastest method to implement web services using Camel and
CXF.</p></div></div><div class="confluence-information-macro
confluence-information-macro-tip"><span class="aui-icon aui-icon-small
aui-iconfont-approve confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When using CXF in streaming modes
(see DataFormat option), then also read about <a shape="rect"
href="stream-caching.html">Stream caching</a>.</p></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.rbtoc1457961505332 {padding: 0px;}
-div.rbtoc1457961505332 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1457961505332 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1458073261585 {padding: 0px;}
+div.rbtoc1458073261585 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1458073261585 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1457961505332">
+/*]]>*/</style></p><div class="toc-macro rbtoc1458073261585">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-URIformat">URI format</a></li><li><a shape="rect"
href="#BookInOnePage-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
@@ -18153,69 +18153,23 @@ queryMap.put("q1", "new&q
queryMap.put("q2", "world");
inMessage.setHeader(CxfConstants.CAMEL_CXF_RS_QUERY_MAP, queryMap);
]]></script>
-</div></div> <h2 id="BookInOnePage-DataSetComponent">DataSet Component</h2>
-
-<a shape="rect" href="testing.html">Testing</a> of distributed and
asynchronous processing is notoriously difficult. The <a shape="rect"
href="mock.html">Mock</a>, <a shape="rect" href="test.html">Test</a> and <a
shape="rect" href="dataset.html">DataSet</a> endpoints work great with the <a
shape="rect" href="testing.html">Camel Testing Framework</a> to simplify your
unit and integration testing using <a shape="rect"
href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a>
and Camel's large range of <a shape="rect"
href="components.html">Components</a> together with the powerful <a
shape="rect" href="bean-integration.html">Bean Integration</a>.
-
-<p>The DataSet component provides a mechanism to easily perform load &
soak testing of your system. It works by allowing you to create <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/dataset/DataSet.html";>DataSet
instances</a> both as a source of messages and as a way to assert that the
data set is received.</p>
-
-<p>Camel will use the <a shape="rect" href="log.html">throughput logger</a>
when sending dataset's. </p>
-
-<h3 id="BookInOnePage-URIformat.14">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
-dataset:name[?options]
+</div></div> <h2 id="BookInOnePage-DataSetComponent">DataSet
Component</h2><p><a shape="rect" href="testing.html">Testing</a> of distributed
and asynchronous processing is notoriously difficult. The <a shape="rect"
href="mock.html">Mock</a>, <a shape="rect" href="test.html">Test</a> and <a
shape="rect" href="dataset.html">DataSet</a> endpoints work great with the <a
shape="rect" href="testing.html">Camel Testing Framework</a> to simplify your
unit and integration testing using <a shape="rect"
href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a>
and Camel's large range of <a shape="rect"
href="components.html">Components</a> together with the powerful <a
shape="rect" href="bean-integration.html">Bean Integration</a>.</p><p>The
DataSet component provides a mechanism to easily perform load & soak
testing of your system. It works by allowing you to create <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/o
rg/apache/camel/component/dataset/DataSet.html">DataSet instances</a> both as
a source of messages and as a way to assert that the data set is
received.</p><p>Camel will use the <a shape="rect" href="log.html">throughput
logger</a> when sending dataset's.</p><h3 id="BookInOnePage-URIformat.14">URI
format</h3><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[dataset:name[?options]
]]></script>
-</div></div>
-
-<p>Where <strong>name</strong> is used to find the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/dataset/DataSet.html";>DataSet
instance</a> in the <a shape="rect" href="registry.html">Registry</a></p>
-
-<p>Camel ships with a support implementation of
<code>org.apache.camel.component.dataset.DataSet</code>, the
<code>org.apache.camel.component.dataset.DataSetSupport</code> class, that can
be used as a base for implementing your own DataSet. Camel also ships with a
default implementation, the
<code>org.apache.camel.component.dataset.SimpleDataSet</code> that can be used
for testing.</p>
-
-<h3 id="BookInOnePage-Options.31">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> 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>produceDelay</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> 3 </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Allows a delay in ms to be specified, which causes
producers to pause in order to simulate slow producers. Uses a minimum of 3 ms
delay unless you set this option to -1 to force no delay at all.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>consumeDelay</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Allows a delay in ms to be specified, which causes
consumers to pause in order to simu
late slow consumers. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>preloadSize</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Sets how many messages should be preloaded (sent)
before the route completes its initialization. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>initialDelay</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000 </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.1:</strong>
Time period in millis to wait before starting sending messages.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>minRate</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Wait until the DataSet contains at least this number
of messages </p></td></tr></tbody></table></div>
-</div>
-
-<p>You can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p>
-
-<h3 id="BookInOnePage-ConfiguringDataSet">Configuring DataSet</h3>
-<p>Camel will lookup in the <a shape="rect" href="registry.html">Registry</a>
for a bean implementing the DataSet interface. So you can register your own
DataSet as:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
- <bean id="myDataSet"
class="com.mycompany.MyDataSet">
+</div></div><p>Where <strong>name</strong> is used to find the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/dataset/DataSet.html";>DataSet
instance</a> in the <a shape="rect"
href="registry.html">Registry</a></p><p>Camel ships with a support
implementation of <code>org.apache.camel.component.dataset.DataSet</code>, the
<code>org.apache.camel.component.dataset.DataSetSupport</code> class, that can
be used as a base for implementing your own DataSet. Camel also ships with some
implementations that can be used for testing:
 <code>org.apache.camel.component.dataset.SimpleDataSet</code>, <code><span>org.apache.camel.component.dataset.ListDataSet</span></code><span>
and </span><code><span><span>org.apache.camel.component.dataset.FileDataSet</span></span></code><span><span>,
all of which extend <code>DataSetSupport</code>.</span></span></p><h3
id="BookInOnePage-Options.31">Options</h3><div clas
s="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>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>produceDelay</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>3</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Allows a delay in ms to be specified, which
causes producers to pause in order to simulate slow producers. Uses a minimum
of 3 ms delay unless you set this option to -1 to force no delay at
all.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>consumeDelay</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Allows a delay in ms to be specified, which causes
consumers to pause in order
to simulate slow consumers.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>preloadSize</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Sets how many messages should be preloaded (sent)
before the route completes its initialization.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>initialDelay</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>1000</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.1:</strong> Time period in
millis to wait before starting sending messages.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>minRate</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Wait until the DataSet contains at least this number of
messages</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<code>dataSetIndex</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><code>lenient</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.17:</strong> Controls the behavior of
the <em>CamelDataSetIndex</em> header. The supported values are
<code>strict</code>, <code>lenient</code> and <code>off</code>. The default
behavior prior to <strong>Camel 2.17</strong> can be restored using
<code><span>dataSetIndex</span>=strict</code></p><p>For consumers:<br
clear="none"> - <code>strict</code> or <code>lenient</code> => The
<em>CamelDataSetIndex</em> header will always be set<br clear="none"> -
<code>off</code> => The <em>CamelDataSetIndex</em> header will not be
set</p><p>For producers:<br clear="none"> - <code>strict</code> => The
<em>CamelDataSetIndex</em> header must be present and the value of the header
will be verified<br clear="none"> - <code>lenient</code> => If the
<em>CamelDataSetIndex</em> header is present, the value of the header wi
ll be verified. If the header is not present, it will be set.<br clear="none">
- <code>off</code> => If the <em>CamelDataSetIndex</em> header is
present, the value of the header will not be verified. If the header is not
present, it will not be set.</p></td></tr></tbody></table></div></div><p>You
can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="BookInOnePage-ConfiguringDataSet">Configuring DataSet</h3><p>Camel will
lookup in the <a shape="rect" href="registry.html">Registry</a> for a bean
implementing the DataSet interface. So you can register your own DataSet
as:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="myDataSet"
class="com.mycompany.MyDataSet">
<property name="size" value="100"/>
</bean>
]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-Example.20">Example</h3>
-
-<p>For example, to test that a set of messages are sent to a queue and then
consumed from the queue without losing any messages:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
-// send the dataset to a queue
+</div></div><h3 id="BookInOnePage-Example.20">Example</h3><p>For example, to
test that a set of messages are sent to a queue and then consumed from the
queue without losing any messages:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[// send the dataset to a queue
from("dataset:foo").to("activemq:SomeQueue");
// now lets test that the messages are consumed correctly
from("activemq:SomeQueue").to("dataset:foo");
]]></script>
-</div></div>
-
-<p>The above would look in the <a shape="rect"
href="registry.html">Registry</a> to find the <strong>foo</strong> DataSet
instance which is used to create the messages.</p>
-
-<p>Then you create a DataSet implementation, such as using the
<code>SimpleDataSet</code> as described below, configuring things like how big
the data set is and what the messages look like etc.</p>
-
-<h3 id="BookInOnePage-PropertiesonSimpleDataSet">Properties on
SimpleDataSet</h3>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p>Property</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>defaultBody</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>Object</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code><hello>world!</hello></code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Specifies the default message body. For
SimpleDataSet it is a constant payload; though if you want to create custom
payloads per message, create your own derivation of
<code>DataSetSupport</code>. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>reportCount</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>long</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>-1</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the number of
messages to be received before reporting progress. Useful for showing progress
of a large load test. If < 0, then <code>size</code> / 5, if is 0 then
<code>size</code>, else set to <code>reportCount</code>
value.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>size</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>long</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>10</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Specifies how many messages to
send/consume.</p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="BookInOnePage-SeeAlso.30">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><li><a shape="rect" href="spring-testing.html">Spring
Testing</a></li></ul> <h2 id="BookInOnePage-Db4oComponent">Db4o Component</h2>
+</div></div><p>The above would look in the <a shape="rect"
href="registry.html">Registry</a> to find the <strong>foo</strong> DataSet
instance which is used to create the messages.</p><p>Then you create a DataSet
implementation, such as using the <code>SimpleDataSet</code> as described
below, configuring things like how big the data set is and what the messages
look like etc.  </p><p> </p><h2
id="BookInOnePage-DataSetSupport(abstractclass)"><code>DataSetSupport</code> (abstract
class)</h2><p>The DataSetSupport abstract class is a nice starting point for
new DataSets, and provides some useful features to derived classes.</p><h3
id="BookInOnePage-PropertiesonDataSetSupport">Properties on
DataSetSupport</h3><div class="confluenceTableSmall"><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Property</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>defaultHeaders</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>Map<String,Object></code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the default message
body. For SimpleDataSet it is a constant payload; though if you want to create
custom payloads per message, create your own derivation of
<code>DataSetSupport</code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>outputTransformer</code></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Processor</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span style="font-family:
monospace;">null</span></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p
> </p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>size</code></p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>long</code></p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>10</code></p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p>Specifies how many messages to
>send/consume.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><code>reportCount</code></td><td colspan="1" rowspan="1"
>class="confluenceTd"><code>long</code></td><td colspan="1" rowspan="1"
>class="confluenceTd"><code>-1</code></td><td colspan="1" rowspan="1"
>class="confluenceTd"><span>Specifies the number of messages to be received
>before reporting progress. Useful for showing progress of a large load test.
>If < 0, then </span><code>size</code><span> / 5, if is 0 then
></span><code>size</code><span>, else set to
></span><code>reportCount</code><span>
>value.</span></td></tr></tbody></table></div></div><h3
>id="BookInOnePage-SimpleDa
taSet"><code>SimpleDataSet</code></h3><p>The <code>SimpleDataSet</code>
extends <code>DataSetSupport</code>, and adds a default body.</p><h3
id="BookInOnePage-AdditionalPropertiesonSimpleDataSet">Additional Properties on
SimpleDataSet</h3><div class="confluenceTableSmall"><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Property</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>defaultBody</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>Object</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code><hello>world!</hello></code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the default message
body. By default, the
<code>SimpleDataSet</code> produces the same constant payload for each
exchange. If you want to customize the payload for each exchange, create a
Camel <code>Processor</code> and configure the <code>SimpleDataSet</code> to
use it by setting the <code>outputTransformer</code>
property.</p></td></tr></tbody></table></div></div><h3
id="BookInOnePage-ListDataSet(Camel2.17)"><code>ListDataSet (Camel
2.17)</code></h3><p>The
List<code>DataSet</code> extends <code>DataSetSupport</code>, and
adds a list of default bodies.</p><h3
id="BookInOnePage-AdditionalPropertiesonListDataSet">Additional Properties on
ListDataSet</h3><div class="confluenceTableSmall"><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Property</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>defaultBodies</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>List<Object></code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>empty
LinkedList<Object></code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Specifies the default message body. By default, the
<code>ListDataSet</code><span> selects a constant payload from the list of
<code>defaultBodies</code> using the <code>CamelDataSetIndex</code>. If you
want to customize the payload, create a Camel </span><code>Processor</code> and
configure the <code>ListDataSet</code><span> to use it by setting the
</span><code>outputTransformer</code><span>
property.</span></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>size</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>long</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>the si
ze of the defaultBodies list</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>Specifies how many messages to send/consume. This
value can be different from the size of the <code>defaultBodies</code> list. If
the value is less than the size of the <code>defaultBodies</code> list, some of
the list elements will not be used. If the value is greater than the size of
the <code>defaultBodies</code> list, the payload for the exchange will be
selected using the modulus of the <code>CamelDataSetIndex</code> and the size
of the <code>defaultBodies</code> list (i.e. <code>CamelDataSetIndex %
defaultBodies.size()</code>
)</span></p></td></tr></tbody></table></div></div><h3
id="BookInOnePage-FileDataSet(Camel2.17)"><code>FileDataSet (Camel
2.17)</code></h3><p>The <code>SimpleDataSet</code> extends
<code>ListDataSet</code>, and adds support for loading the bodies from a
file.</p><h3 id="BookInOnePage-AdditionalPropertiesonFileDataSet">Additional
Properties on FileDataSe
t</h3><div class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Property</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>sourceFile</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>File</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span style="font-family:
monospace;">null</span></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Specifies the source file for
payloads</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>delimiter</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><span style="
font-family: monospace;">\z</span></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Specifies the delimiter pattern used by a
<code>java.util.Scanner</code> to split the file into multiple
payloads.</p></td></tr></tbody></table></div></div><p></p><h3
id="BookInOnePage-SeeAlso.30">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><li><a
shape="rect" href="spring-testing.html">Spring Testing</a></li></ul> <h2
id="BookInOnePage-Db4oComponent">Db4o Component</h2>
<p><strong>Available as of Camel 2.5</strong></p>
<p>The <strong>db4o:</strong> component allows you to work with <a
shape="rect" class="external-link" href="http://www.db4o.com";
rel="nofollow">db4o</a> NoSQL database. The camel-db4o library is provided by
the <a shape="rect" class="external-link"
href="http://code.google.com/p/camel-extra/"; rel="nofollow">Camel Extra</a>
project which hosts all *GPL related components for Camel.</p>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
