Author: buildbot Date: Fri Feb 7 16:19:09 2014 New Revision: 896757 Log: Production update by buildbot for camel
Modified: websites/production/camel/content/cache/main.pageCache websites/production/camel/content/springbatch.html websites/production/camel/content/vertx.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 Fri Feb 7 16:19:09 2014 @@ -85,96 +85,38 @@ <tbody> <tr> <td valign="top" width="100%"> -<div class="wiki-content maincontent"><h2 id="SpringBatch-SpringBatchComponent">Spring Batch Component</h2> - -<p>The <strong>spring-batch:</strong> component and support classes provide integration bridge between Camel and <a shape="rect" class="external-link" href="http://www.springsource.org/spring-batch" rel="nofollow">Spring Batch</a> infrastructure.</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: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ -<dependency> +<div class="wiki-content maincontent"><h2 id="SpringBatch-SpringBatchComponent">Spring Batch Component</h2><p>The <strong>spring-batch:</strong> component and support classes provide integration bridge between Camel and <a shape="rect" class="external-link" href="http://www.springsource.org/spring-batch" rel="nofollow">Spring Batch</a> infrastructure.</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: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-spring-batch</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> ]]></script> -</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="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ -spring-batch:jobName[?options] +</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="theme: Default; brush: java; gutter: false" 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="aui-message problem shadowed information-macro"> +</div></div><p>Where <strong>jobName</strong> represents the name of the Spring Batch job located in the Camel registry.</p> <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 Spring Batch 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 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>null</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>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="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ -from("direct:startBatch").to("spring-batch:myJob"); +<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>null</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>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>J obLauncher</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="theme: Default; brush: java; gutter: false" 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"> -<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ -from("direct:startBatch").to("spring-batch:myJob?jobLauncherRef=myJobLauncher"); +</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"> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("direct:startBatch").to("spring-batch:myJob?jobLauncherRef=myJobLauncher"); ]]></script> -</div></div> - -<p>Starting from the Camel <strong>2.11.1</strong> <code>JobExecution</code> instance returned by the <code>JobLauncher</code> is forwarded by the <code>SpringBatchProducer</code> as the output message. You can use the <code>JobExecution</code> instance to perform some operations using the Spring Batch API directly.</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:startBatch").to("spring-batch:myJob").to("mock:JobExecutions"); +</div></div><p>Starting from the Camel <strong>2.11.1</strong> <code>JobExecution</code> instance returned by the <code>JobLauncher</code> is forwarded by the <code>SpringBatchProducer</code> as the output message. You can use the <code>JobExecution</code> instance to perform some operations using the Spring Batch API directly.</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:startBatch").to("spring-batch:myJob").to("mock:JobExecutions"); ... MockEndpoint mockEndpoint = ...; JobExecution jobExecution = mockEndpoint.getExchanges().get(0).getIn().getBody(JobExecution.class); BatchStatus currentJobStatus = jobExecution.getStatus(); ]]></script> -</div></div> - -<h3 id="SpringBatch-Supportclasses">Support classes</h3> - -<p>Apart from the Component, Camel Spring Batch provides also support classes, which can be used to hook into Spring Batch infrastructure.</p> - -<h4 id="SpringBatch-CamelItemReader">CamelItemReader</h4> - -<p><code>CamelItemReader</code> can be used to read batch data directly from the Camel infrastructure.</p> - -<p>For example the snippet below configures Spring Batch to read data from JMS queue.</p> - -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ -<bean id="camelReader" class="org.apache.camel.component.spring.batch.support.CamelItemReader"> +</div></div><h3 id="SpringBatch-Supportclasses">Support classes</h3><p>Apart from the Component, Camel Spring Batch provides also support classes, which can be used to hook into Spring Batch infrastructure.</p><h4 id="SpringBatch-CamelItemReader">CamelItemReader</h4><p><code>CamelItemReader</code> can be used to read batch data directly from the Camel infrastructure.</p><p>For example the snippet below configures Spring Batch to read data from JMS queue.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<bean id="camelReader" class="org.apache.camel.component.spring.batch.support.CamelItemReader"> <constructor-arg ref="consumerTemplate"/> <constructor-arg value="jms:dataQueue"/> </bean> @@ -187,40 +129,22 @@ BatchStatus currentJobStatus = jobExecut </batch:step> </batch:job> ]]></script> -</div></div> - -<h4 id="SpringBatch-CamelItemWriter">CamelItemWriter</h4> - -<p><code>CamelItemWriter</code> has similar purpose as <code>CamelItemReader</code>, but it is dedicated to write chunk of the processed data.</p> - -<p>For example the snippet below configures Spring Batch to read data from JMS queue.</p> - -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ -<bean id="camelReader" class="org.apache.camel.component.spring.batch.support.CamelItemReader"> - <constructor-arg ref="consumerTemplate"/> +</div></div><h4 id="SpringBatch-CamelItemWriter">CamelItemWriter</h4><p><code>CamelItemWriter</code> has similar purpose as <code>CamelItemReader</code>, but it is dedicated to write chunk of the processed data.</p><p>For example the snippet below configures Spring Batch to read data from JMS queue.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<bean id="camelwriter" class="org.apache.camel.component.spring.batch.support.CamelItemWriter"> + <constructor-arg ref="producerTemplate"/> <constructor-arg value="jms:dataQueue"/> </bean> <batch:job id="myJob"> <batch:step id="step"> <batch:tasklet> - <batch:chunk reader="camelReader" writer="someWriter" commit-interval="100"/> + <batch:chunk reader="someReader" writer="camelwriter" commit-interval="100"/> </batch:tasklet> </batch:step> </batch:job> ]]></script> -</div></div> - -<h4 id="SpringBatch-CamelItemProcessor">CamelItemProcessor</h4> - -<p><code>CamelItemProcessor</code> is the implementation of Spring Batch <code>org.springframework.batch.item.ItemProcessor</code> interface. The latter implementation relays on <a shape="rect" class="external-link" href="http://camel.apache.org/request-reply.html">Request Reply pattern</a> to delegate the processing of the batch item to the Camel infrastructure. The item to process is sent to the Camel endpoint as the body of the message.</p> - -<p>For example the snippet below performs simple processing of the batch item using the <a shape="rect" class="external-link" href="http://camel.apache.org/direct.html">Direct endpoint </a> and the <a shape="rect" class="external-link" href="http://camel.apache.org/simple.html">Simple expression language </a>.</p> - -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ -<camel:camelContext> +</div></div><h4 id="SpringBatch-CamelItemProcessor">CamelItemProcessor</h4><p><code>CamelItemProcessor</code> is the implementation of Spring Batch <code>org.springframework.batch.item.ItemProcessor</code> interface. The latter implementation relays on <a shape="rect" class="external-link" href="http://camel.apache.org/request-reply.html">Request Reply pattern</a> to delegate the processing of the batch item to the Camel infrastructure. The item to process is sent to the Camel endpoint as the body of the message.</p><p>For example the snippet below performs simple processing of the batch item using the <a shape="rect" class="external-link" href="http://camel.apache.org/direct.html">Direct endpoint </a> and the <a shape="rect" class="external-link" href="http://camel.apache.org/simple.html">Simple expression language </a>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<camel:camelContext> <camel:route> <camel:from uri="direct:processor"/> <camel:setExchangePattern pattern="InOut"/> @@ -243,20 +167,8 @@ BatchStatus currentJobStatus = jobExecut </batch:step> </batch:job> ]]></script> -</div></div> - - -<h4 id="SpringBatch-CamelJobExecutionListener">CamelJobExecutionListener</h4> - -<p><code>CamelJobExecutionListener</code> is the implementation of the <code>org.springframework.batch.core.JobExecutionListener</code> interface sending job execution events to the Camel endpoint.</p> - -<p>The <code>org.springframework.batch.core.JobExecution</code> instance produced by the Spring Batch is sent as a body of the message. To distinguish between before- and after-callbacks <code>SPRING_BATCH_JOB_EVENT_TYPE</code> header is set to the <code>BEFORE</code> or <code>AFTER</code> value.</p> - -<p>The example snippet below sends Spring Batch job execution events to the JMS queue.</p> - -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ -<bean id="camelJobExecutionListener" class="org.apache.camel.component.spring.batch.support.CamelJobExecutionListener"> +</div></div><h4 id="SpringBatch-CamelJobExecutionListener">CamelJobExecutionListener</h4><p><code>CamelJobExecutionListener</code> is the implementation of the <code>org.springframework.batch.core.JobExecutionListener</code> interface sending job execution events to the Camel endpoint.</p><p>The <code>org.springframework.batch.core.JobExecution</code> instance produced by the Spring Batch is sent as a body of the message. To distinguish between before- and after-callbacks <code>SPRING_BATCH_JOB_EVENT_TYPE</code> header is set to the <code>BEFORE</code> or <code>AFTER</code> value.</p><p>The example snippet below sends Spring Batch job execution events to the JMS queue.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<bean id="camelJobExecutionListener" class="org.apache.camel.component.spring.batch.support.CamelJobExecutionListener"> <constructor-arg ref="producerTemplate"/> <constructor-arg value="jms:batchEventsBus"/> </bean> Modified: websites/production/camel/content/vertx.html ============================================================================== --- websites/production/camel/content/vertx.html (original) +++ websites/production/camel/content/vertx.html Fri Feb 7 16:19:09 2014 @@ -85,37 +85,18 @@ <tbody> <tr> <td valign="top" width="100%"> -<div class="wiki-content maincontent"><h2 id="Vertx-VertxComponent">Vertx Component</h2> - -<p><strong>Available as of Camel 2.12</strong></p> - -<p>The <strong>vertx</strong> component is for working with the <a shape="rect" class="external-link" href="http://vertx.io/" rel="nofollow">Vertx</a> <a shape="rect" class="external-link" href="http://vertx.io/core_manual_js.html#the-event-bus" rel="nofollow">EventBus</a>.</p> - -<p>The vertx <a shape="rect" class="external-link" href="http://vertx.io/core_manual_js.html#the-event-bus" rel="nofollow">EventBus</a> sends and receives JSON events.</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: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ -<dependency> +<div class="wiki-content maincontent"><h2 id="Vertx-VertxComponent">Vertx Component</h2><p><strong>Available as of Camel 2.12</strong></p><p>The <strong>vertx</strong> component is for working with the <a shape="rect" class="external-link" href="http://vertx.io/" rel="nofollow">Vertx</a> <a shape="rect" class="external-link" href="http://vertx.io/core_manual_js.html#the-event-bus" rel="nofollow">EventBus</a>.</p><p>The vertx <a shape="rect" class="external-link" href="http://vertx.io/core_manual_js.html#the-event-bus" rel="nofollow">EventBus</a> sends and receives JSON events.</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: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-vertx</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> ]]></script> -</div></div> - -<h3 id="Vertx-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[ -vertx:channelName[?options] +</div></div><h3 id="Vertx-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[vertx:channelName[?options] ]]></script> -</div></div> - -<p>At the moment, there are no options for this component. Any future release could change this, so please check back.</p> - -<h3 id="Vertx-SeeAlso">See Also</h3> +</div></div><h3 id="Vertx-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>pubSub</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.3:</strong> Whether to use publish/subscribe instead of point to point when sending to a vertx endpoint.</p></td></tr></tbody></table></div><pre>You can append query options to the URI in the following format, ?option=value&option=value&...</pre><p> </p><p></p><h3 id="Vertx-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></div> </td> <td valign="top">