Author: buildbot
Date: Sat May 28 07:20:04 2016
New Revision: 989411
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/springbatch.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/springbatch.html
==============================================================================
--- websites/production/camel/content/springbatch.html (original)
+++ websites/production/camel/content/springbatch.html Sat May 28 07:20:04 2016
@@ -96,7 +96,7 @@
</div></div><h3 id="SpringBatch-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[spring-batch:jobName[?options]
]]></script>
-</div></div><p>Where <strong>jobName</strong> represents the name of the
Spring Batch job located in the Camel registry.</p><div
class="confluence-information-macro confluence-information-macro-warning"><span
class="aui-icon aui-icon-small aui-iconfont-error
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>This component can only be used to
define producer endpoints, which means that you cannot use the Spring Batch
component in a <code>from()</code> statement.</p></div></div><h3
id="SpringBatch-Options">Options</h3><div class="table-wrap"><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>jobLauncherRef</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>n
ull</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Deprecated and will be removed in Camel
3.0!</strong> <strong>Camel 2.10:</strong> Use jobLauncher=#theName
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>jobLauncher</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.11.1:</strong> Explicitly
specifies a <code>JobLauncher</code> to be used from the Camel <a shape="rect"
href="registry.html">Registry</a>.</p></td></tr></tbody></table></div><h3
id="SpringBatch-Usage">Usage</h3><p>When Spring Batch component receives the
message, it triggers the job execution. The job will be executed using the
<code>org.springframework.batch.core.launch.JobLaucher</code> instance resolved
according to the following algorithm:</p><ul><li>if <code>JobLauncher</code> is
manually set on the component, then use it.</li><li>if <code>j
obLauncherRef</code> option is set on the component, then search Camel <a
shape="rect" href="registry.html">Registry</a> for the <code>JobLauncher</code>
with the given name. <strong>Deprecated and will be removed in Camel
3.0!</strong></li><li>if there is <code>JobLauncher</code> registered in the
Camel <a shape="rect" href="registry.html">Registry</a> under
<strong>jobLauncher</strong> name, then use it.</li><li>if none of the steps
above allow to resolve the <code>JobLauncher</code> and there is exactly one
<code>JobLauncher</code> instance in the Camel <a shape="rect"
href="registry.html">Registry</a>, then use it.</li></ul><p>All headers found
in the message are passed to the <code>JobLauncher</code> as job parameters.
<code>String</code>, <code>Long</code>, <code>Double</code> and
<code>java.util.Date</code> values are copied to the
<code>org.springframework.batch.core.JobParametersBuilder</code> - other data
types are converted to Strings.</p><h3 id="SpringBatch-Examples">Exa
mples</h3><p>Triggering the Spring Batch job execution:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Where <strong>jobName</strong> represents the name of the
Spring Batch job located in the Camel registry.</p><div
class="confluence-information-macro confluence-information-macro-warning"><span
class="aui-icon aui-icon-small aui-iconfont-error
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>This component can only be used to
define producer endpoints, which means that you cannot use the Spring Batch
component in a <code>from()</code> statement.</p></div></div><h3
id="SpringBatch-Options">Options</h3><div class="table-wrap"><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>jobLauncherRef</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>n
ull</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Deprecated and will be removed in Camel
3.0!</strong> <strong>Camel 2.10:</strong> Use jobLauncher=#theName
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>jobLauncher</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.11.1:</strong> Explicitly
specifies a <code>JobLauncher</code> to be used from the Camel <a shape="rect"
href="registry.html">Registry</a>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>jobFromHeader</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><code>false</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><strong>Camel 2.18:</strong> Explicitly defines if the
jobName shouls be taken from the headers instead of the URI. The header has
name: <code>CamelSpringBatchJobName</code></td></tr></tbody></ta
ble></div><h3 id="SpringBatch-Usage">Usage</h3><p>When Spring Batch component
receives the message, it triggers the job execution. The job will be executed
using the <code>org.springframework.batch.core.launch.JobLaucher</code>
instance resolved according to the following algorithm:</p><ul><li>if
<code>JobLauncher</code> is manually set on the component, then use
it.</li><li>if <code>jobLauncherRef</code> option is set on the component, then
search Camel <a shape="rect" href="registry.html">Registry</a> for the
<code>JobLauncher</code> with the given name. <strong>Deprecated and will be
removed in Camel 3.0!</strong></li><li>if there is <code>JobLauncher</code>
registered in the Camel <a shape="rect" href="registry.html">Registry</a> under
<strong>jobLauncher</strong> name, then use it.</li><li>if none of the steps
above allow to resolve the <code>JobLauncher</code> and there is exactly one
<code>JobLauncher</code> instance in the Camel <a shape="rect"
href="registry.html">Registry<
/a>, then use it.</li></ul><p>All headers found in the message are passed to
the <code>JobLauncher</code> as job parameters. <code>String</code>,
<code>Long</code>, <code>Double</code> and <code>java.util.Date</code> values
are copied to the
<code>org.springframework.batch.core.JobParametersBuilder</code> - other data
types are converted to Strings.</p><h3
id="SpringBatch-Examples">Examples</h3><p>Triggering the Spring Batch job
execution:</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[from("direct:startBatch").to("spring-batch:myJob");
]]></script>
</div></div><p>Triggering the Spring Batch job execution with the
<code>JobLauncher</code> set explicitly.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
