Author: buildbot
Date: Mon Mar 14 19:19:53 2016
New Revision: 982778
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/dataset.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/dataset.html
==============================================================================
--- websites/production/camel/content/dataset.html (original)
+++ websites/production/camel/content/dataset.html Mon Mar 14 19:19:53 2016
@@ -85,69 +85,23 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2
id="DataSet-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="DataSet-URIformat">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 class="wiki-content maincontent"><h2
id="DataSet-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/c
amel-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="DataSet-URIformat">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="DataSet-Options">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="DataSet-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 a
default implementation, the
<code>org.apache.camel.component.dataset.SimpleDataSet</code> that can be used
for testing.</p><h3 id="DataSet-Options">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="confluen
ceTh"><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 s
hould 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">lenient</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>st
rict</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 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><p> </p></td></t
r></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="DataSet-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="DataSet-Example">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="DataSet-Example">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="DataSet-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="DataSet-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><li><a shape="rect" href="spring-testing.html">Spring
Testing</a></li></ul></div>
+</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="DataSet-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><p></p><h3
>id="DataSet-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><li><a
shape="rect" href="spring-testing.html">Spring Testing</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
