camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r929977 [2/2] - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache quartz.html quartz2.html
Date Fri, 21 Nov 2014 14:19:16 GMT
Modified: websites/production/camel/content/quartz.html
==============================================================================
--- websites/production/camel/content/quartz.html (original)
+++ websites/production/camel/content/quartz.html Fri Nov 21 14:19:16 2014
@@ -86,172 +86,58 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Quartz-QuartzComponent">Quartz Component</h2>
-
-<p>The <strong>quartz:</strong> component provides a scheduled delivery of messages using the <a shape="rect" class="external-link" href="http://www.quartz-scheduler.org/" rel="nofollow">Quartz Scheduler 1.x </a>. <br clear="none">
-Each endpoint represents a different timer (in Quartz terms, a Trigger and JobDetail).</p>
-
-    <div class="aui-message success shadowed information-macro">
+<div class="wiki-content maincontent"><h2 id="Quartz-QuartzComponent">Quartz Component</h2><p>The <strong>quartz:</strong> component provides a scheduled delivery of messages using the <a shape="rect" class="external-link" href="http://www.quartz-scheduler.org/" rel="nofollow">Quartz Scheduler 1.x </a>. <br clear="none"> Each endpoint represents a different timer (in Quartz terms, a Trigger and JobDetail).</p>    <div class="aui-message success shadowed information-macro">
                             <span class="aui-icon icon-success">Icon</span>
                 <div class="message-content">
-                            
-<p>If you are using Quartz 2.x then from Camel 2.12 onwards there is a <a shape="rect" href="quartz2.html">Quartz2</a> component you should use</p>
+                            <p>If you are using Quartz 2.x then from Camel 2.12 onwards there is a <a shape="rect" href="quartz2.html">Quartz2</a> component you should use</p>
                     </div>
     </div>
-
-
-<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[
-&lt;dependency&gt;
+<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[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-quartz&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div>
-
-<h3 id="Quartz-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[
-quartz://timerName?options
+</div></div><h3 id="Quartz-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[quartz://timerName?options
 quartz://groupName/timerName?options
 quartz://groupName/timerName?cron=expression
 quartz://timerName?cron=expression
 ]]></script>
-</div></div>
-
-<p>The component uses either a <code>CronTrigger</code> or a <code>SimpleTrigger</code>. If no cron expression is provided, the component uses a simple trigger. If no <code>groupName</code> is provided, the quartz component uses the <code>Camel</code> group name.</p>
-
-<p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p>
-
-<h3 id="Quartz-Options">Options</h3>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Parameter </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>cron</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>None</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies a <code>cron</code> expression (not compatible with the <code>trigger.*</code> or <code>job.*</code> options). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>trigger.repeatCount</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> SimpleTrigger: How many times should the timer repeat? </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>t
 rigger.repeatInterval</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> SimpleTrigger: The amount of time in milliseconds between repeated triggers. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>job.name</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets the job name. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>job.<em>XXX</em></code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets the job option with the <code><em>XXX</em></code> setter name. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>trigger.<em>XXX</em></code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </
 p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets the trigger option with the <code><em>XXX</em></code> setter name. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>stateful</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Uses a Quartz <code>StatefulJob</code> instead of the default job. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>fireNow</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> New to Camel 2.2.0, if it is true will fire the trigger when the route is start when using SimpleTrigger.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>deleteJob</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="conf
 luenceTd"><p> <strong>Camel 2.12:</strong> If set to true, then the trigger automatically delete when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>pauseJob</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12:</strong> If set to true, then the trigger automatically pauses when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true. </p></td></tr></tbody></table></div>
-</div>
-
-<p>For example, the following routing rule will fire two timer events to the <code>mock:results</code> endpoint:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>The component uses either a <code>CronTrigger</code> or a <code>SimpleTrigger</code>. If no cron expression is provided, the component uses a simple trigger. If no <code>groupName</code> is provided, the quartz component uses the <code>Camel</code> group name.</p><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p><h3 id="Quartz-Options">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter</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>cron</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><em>None</em></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies a <code>cron</code> expres
 sion (not compatible with the <code>trigger.*</code> or <code>job.*</code> options).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>trigger.repeatCount</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>SimpleTrigger: How many times should the timer repeat?</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>trigger.repeatInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>SimpleTrigger: The amount of time in milliseconds between repeated triggers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>job.name</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the job name.</p></td></tr><tr><td colspan="1" rowspan="1" class="con
 fluenceTd"><p><code>job.<em>XXX</em></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the job option with the <code><em>XXX</em></code> setter name.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>trigger.<em>XXX</em></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the trigger option with the <code><em>XXX</em></code> setter name.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>stateful</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses a Quartz <code>StatefulJob</code> instead of the default job.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>fireNow</code></p></td><td colspan="1" rowspan="1" class="conf
 luenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>New to Camel 2.2.0, if it is true will fire the trigger when the route is start when using SimpleTrigger.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>deleteJob</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong> If set to true, then the trigger automatically delete when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>pauseJob</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><str
 ong>Camel 2.12:</strong> If set to true, then the trigger automatically pauses when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>usingFixedCamelContextName</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong><strong>Camel 2.15.0: </strong></strong><span><span>If it is true, <span>JobDataMap </span></span></span><span>uses the CamelContext name directly to reference the camel context, </span><span>if it is false, <span>JobDataMap </span><span>uses </span>use the CamelContext management name which could be changed during the deploy time.</span></td></tr></tbody></table></div></div><p>For example, the following routing rule will f
 ire two timer events to the <code>mock:results</code> endpoint:</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[
 from(&quot;quartz://myGroup/myTimerName?trigger.repeatInterval=2&amp;trigger.repeatCount=1&quot;).routeId(&quot;myRoute&quot;).to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>When using a <a shape="rect" class="external-link" href="http://quartz-scheduler.org/api/2.0.0/org/quartz/StatefulJob.html" rel="nofollow">StatefulJob</a>, the <a shape="rect" class="external-link" href="http://quartz-scheduler.org/api/2.0.0/org/quartz/JobDataMap.html" rel="nofollow">JobDataMap</a> is re-persisted after every execution of the job, thus preserving state for the next execution.</p>
-
-    <div class="aui-message hint shadowed information-macro">
+</div></div><p>When using a <a shape="rect" class="external-link" href="http://quartz-scheduler.org/api/2.0.0/org/quartz/StatefulJob.html" rel="nofollow">StatefulJob</a>, the <a shape="rect" class="external-link" href="http://quartz-scheduler.org/api/2.0.0/org/quartz/JobDataMap.html" rel="nofollow">JobDataMap</a> is re-persisted after every execution of the job, thus preserving state for the next execution.</p>    <div class="aui-message hint shadowed information-macro">
                     <p class="title">Running in OSGi and having multiple bundles with quartz routes</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">
-                            
-<p>If you run in OSGi such as Apache ServiceMix, or Apache Karaf, and have multiple bundles with Camel routes that start from <a shape="rect" href="quartz.html">Quartz</a> endpoints, then make sure if you assign<br clear="none">
-an <code>id</code> to the &lt;camelContext&gt; that this id is unique, as this is required by the <code>QuartzScheduler</code> in the OSGi container. If you do not set any <code>id</code> on &lt;camelContext&gt; then<br clear="none">
-a unique id is auto assigned, and there is no problem.</p>
+                            <p>If you run in OSGi such as Apache ServiceMix, or Apache Karaf, and have multiple bundles with Camel routes that start from <a shape="rect" href="quartz.html">Quartz</a> endpoints, then make sure if you assign<br clear="none"> an <code>id</code> to the &lt;camelContext&gt; that this id is unique, as this is required by the <code>QuartzScheduler</code> in the OSGi container. If you do not set any <code>id</code> on &lt;camelContext&gt; then<br clear="none"> a unique id is auto assigned, and there is no problem.</p>
                     </div>
     </div>
-
-
-<h3 id="Quartz-Configuringquartz.propertiesfile">Configuring quartz.properties file</h3>
-
-<p>By default Quartz will look for a <code>quartz.properties</code> file in the <code>org/quartz</code> directory of the classpath. If you are using WAR deployments this means just drop the quartz.properties in <code>WEB-INF/classes/org/quartz</code>.</p>
-
-<p>However the Camel <a shape="rect" href="quartz.html">Quartz</a> component also allows you to configure properties:</p>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Parameter </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>properties</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Properties</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.4</strong>: You can configure a <code>java.util.Properties</code> instance. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>propertiesFile</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <
 code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.4</strong>: File name of the properties to load from the classpath </p></td></tr></tbody></table></div>
-</div>
-
-<p>To do this you can configure this in Spring XML as follows</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[
-&lt;bean id=&quot;quartz&quot; class=&quot;org.apache.camel.component.quartz.QuartzComponent&quot;&gt;
+<h3 id="Quartz-Configuringquartz.propertiesfile">Configuring quartz.properties file</h3><p>By default Quartz will look for a <code>quartz.properties</code> file in the <code>org/quartz</code> directory of the classpath. If you are using WAR deployments this means just drop the quartz.properties in <code>WEB-INF/classes/org/quartz</code>.</p><p>However the Camel <a shape="rect" href="quartz.html">Quartz</a> component also allows you to configure properties:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</c
 ode></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Properties</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.4</strong>: You can configure a <code>java.util.Properties</code> instance.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>propertiesFile</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.4</strong>: File name of the properties to load from the classpath</p></td></tr></tbody></table></div></div><p>To do this you can configure this in Spring XML as follows</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[&lt;bean id=&quot;quartz&quot; class=&quot;org.apache.camel.component.quartz.QuartzComponent&quot;&gt;
     &lt;property name=&quot;propertiesFile&quot; value=&quot;com/mycompany/myquartz.properties&quot;/&gt;
 &lt;/bean&gt;
 ]]></script>
-</div></div>
-
-<h3 id="Quartz-EnablingQuartzschedulerinJMX">Enabling Quartz scheduler in JMX</h3>
-
-<p>You need to configure the quartz scheduler properties to enable JMX.<br clear="none">
-That is typically setting the option <code>"org.quartz.scheduler.jmx.export"</code> to a <code>true</code> value in the configuration file.</p>
-
-<p>From Camel 2.13 onwards Camel will automatic set this option to true, unless explicit disabled.</p>
-
-<h3 id="Quartz-StartingtheQuartzscheduler">Starting the Quartz scheduler</h3>
-<p><strong>Available as of Camel 2.4</strong></p>
-
-<p>The <a shape="rect" href="quartz.html">Quartz</a> component offers an option to let the Quartz scheduler be started delayed, or not auto started at all.</p>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Parameter </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>startDelayedSeconds</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.4</strong>: Seconds to wait before starting the quartz scheduler. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>autoStartScheduler</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bo
 olean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.4:</strong> Whether or not the scheduler should be auto started. </p></td></tr></tbody></table></div>
-</div>
-
-<p>To do this you can configure this in Spring XML as follows</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[
-&lt;bean id=&quot;quartz&quot; class=&quot;org.apache.camel.component.quartz.QuartzComponent&quot;&gt;
+</div></div><h3 id="Quartz-EnablingQuartzschedulerinJMX">Enabling Quartz scheduler in JMX</h3><p>You need to configure the quartz scheduler properties to enable JMX.<br clear="none"> That is typically setting the option <code>"org.quartz.scheduler.jmx.export"</code> to a <code>true</code> value in the configuration file.</p><p>From Camel 2.13 onwards Camel will automatic set this option to true, unless explicit disabled.</p><h3 id="Quartz-StartingtheQuartzscheduler">Starting the Quartz scheduler</h3><p><strong>Available as of Camel 2.4</strong></p><p>The <a shape="rect" href="quartz.html">Quartz</a> component offers an option to let the Quartz scheduler be started delayed, or not auto started at all.</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceT
 h"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>startDelayedSeconds</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.4</strong>: Seconds to wait before starting the quartz scheduler.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>autoStartScheduler</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.4:</strong> Whether or not the scheduler should be auto started.</p></td></tr></tbody></table></div></div><p>To do this you can configure this in Spring XML as follows</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[&lt;bean id=&quot;quartz&quot; class=&quot;org.apache.camel.component.quartz.QuartzComponent&quot;&gt;
     &lt;property name=&quot;startDelayedSeconds&quot; value=&quot;5&quot;/&gt;
 &lt;/bean&gt;
 ]]></script>
-</div></div>
-
-
-<h3 id="Quartz-Clustering">Clustering</h3>
-<p><strong>Available as of Camel 2.4</strong></p>
-
-<p>If you use Quartz in clustered mode, e.g. the <code>JobStore</code> is clustered. Then from Camel 2.4 onwards the <a shape="rect" href="quartz.html">Quartz</a> component will <strong>not</strong> pause/remove triggers when a node is being stopped/shutdown. This allows the trigger to keep running on the other nodes in the cluster.</p>
-
-<p><strong>Note</strong>: When running in clustered node no checking is done to ensure unique job name/group for endpoints. </p>
-
-
-<h3 id="Quartz-MessageHeaders">Message Headers</h3>
-<p>Camel adds the getters from the Quartz Execution Context as header values. The following headers are added:<br clear="none">
-<code>calendar</code>, <code>fireTime</code>, <code>jobDetail</code>, <code>jobInstance</code>, <code>jobRuntTime</code>, <code>mergedJobDataMap</code>, <code>nextFireTime</code>, <code>previousFireTime</code>, <code>refireCount</code>, <code>result</code>, <code>scheduledFireTime</code>, <code>scheduler</code>, <code>trigger</code>, <code>triggerName</code>, <code>triggerGroup</code>.</p>
-
-<p>The <code>fireTime</code> header contains the <code>java.util.Date</code> of when the exchange was fired.</p>
-
-<h3 id="Quartz-UsingCronTriggers">Using Cron Triggers</h3>
-<p>Quartz supports <a shape="rect" class="external-link" href="http://www.quartz-scheduler.org/documentation/quartz-2.1.x/tutorials/crontrigger" rel="nofollow">Cron-like expressions</a> for specifying timers in a handy format. You can use these expressions in the <code>cron</code> URI parameter; though to preserve valid URI encoding we allow + to be used instead of spaces. Quartz provides a <a shape="rect" class="external-link" href="http://www.quartz-scheduler.org/docs/tutorials/crontrigger.html" rel="nofollow">little tutorial</a> on how to use cron expressions.</p>
-
-<p>For example, the following will fire a message every five minutes starting at 12pm (noon) to 6pm on weekdays:</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(&quot;quartz://myGroup/myTimerName?cron=0+0/5+12-18+?+*+MON-FRI&quot;).to(&quot;activemq:Totally.Rocks&quot;);
+</div></div><h3 id="Quartz-Clustering">Clustering</h3><p><strong>Available as of Camel 2.4</strong></p><p>If you use Quartz in clustered mode, e.g. the <code>JobStore</code> is clustered. Then from Camel 2.4 onwards the <a shape="rect" href="quartz.html">Quartz</a> component will <strong>not</strong> pause/remove triggers when a node is being stopped/shutdown. This allows the trigger to keep running on the other nodes in the cluster.</p><p><strong>Note</strong>: When running in clustered node no checking is done to ensure unique job name/group for endpoints.</p><h3 id="Quartz-MessageHeaders">Message Headers</h3><p>Camel adds the getters from the Quartz Execution Context as header values. The following headers are added:<br clear="none"> <code>calendar</code>, <code>fireTime</code>, <code>jobDetail</code>, <code>jobInstance</code>, <code>jobRuntTime</code>, <code>mergedJobDataMap</code>, <code>nextFireTime</code>, <code>previousFireTime</code>, <code>refireCount</code>, <code>result<
 /code>, <code>scheduledFireTime</code>, <code>scheduler</code>, <code>trigger</code>, <code>triggerName</code>, <code>triggerGroup</code>.</p><p>The <code>fireTime</code> header contains the <code>java.util.Date</code> of when the exchange was fired.</p><h3 id="Quartz-UsingCronTriggers">Using Cron Triggers</h3><p>Quartz supports <a shape="rect" class="external-link" href="http://www.quartz-scheduler.org/documentation/quartz-2.1.x/tutorials/crontrigger" rel="nofollow">Cron-like expressions</a> for specifying timers in a handy format. You can use these expressions in the <code>cron</code> URI parameter; though to preserve valid URI encoding we allow + to be used instead of spaces. Quartz provides a <a shape="rect" class="external-link" href="http://www.quartz-scheduler.org/docs/tutorials/crontrigger.html" rel="nofollow">little tutorial</a> on how to use cron expressions.</p><p>For example, the following will fire a message every five minutes starting at 12pm (noon) to 6pm on weekdays:
 </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(&quot;quartz://myGroup/myTimerName?cron=0+0/5+12-18+?+*+MON-FRI&quot;).to(&quot;activemq:Totally.Rocks&quot;);
 ]]></script>
-</div></div>
-
-<p>which is equivalent to using the cron expression</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[
-0 0/5 12-18 ? * MON-FRI
+</div></div><p>which is equivalent to using the cron expression</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[0 0/5 12-18 ? * MON-FRI
 ]]></script>
-</div></div>
-
-<p>The following table shows the URI character encodings we use to preserve valid URI syntax:</p>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>URI Character</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Cron character</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>+</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>Space</em> </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="Quartz-Specifyingtimezone">Specifying time zone</h3>
-<p><strong>Available as of Camel 2.8.1</strong><br clear="none">
-The Quartz Scheduler allows you to configure time zone per trigger. For example to use a timezone of your country, then you can do as follows:</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[
-quartz://groupName/timerName?cron=0+0/5+12-18+?+*+MON-FRI&amp;trigger.timeZone=Europe/Stockholm
-]]></script>
-</div></div>
-
-<p>The timeZone value is the values accepted by <code>java.util.TimeZone</code>.</p>
-
-<p>In Camel 2.8.0 or older versions you would have to provide your custom <code>String</code> to <code>java.util.TimeZone</code> <a shape="rect" href="type-converter.html">Type Converter</a> to be able configure this from the endpoint uri.<br clear="none">
-From Camel 2.8.1 onwards we have included such a <a shape="rect" href="type-converter.html">Type Converter</a> in the camel-core.</p>
-
-<h3 id="Quartz-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="quartz2.html">Quartz2</a></li><li><a shape="rect" href="timer.html">Timer</a></li></ul></div>
+</div></div><p>The following table shows the URI character encodings we use to preserve valid URI syntax:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>URI Character</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Cron character</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>+</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><em>Space</em></p></td></tr></tbody></table></div></div><h3 id="Quartz-Specifyingtimezone">Specifying time zone</h3><p><strong>Available as of Camel 2.8.1</strong><br clear="none"> The Quartz Scheduler allows you to configure time zone per trigger. For example to use a timezone of your country, then you can do as follows:</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[quartz://groupName/timerName?cron=0+0/5+12-18+?+*+MON-FRI&amp;trigger.timeZone=Europe/Stockholm
+]]></script>
+</div></div><p>The timeZone value is the values accepted by <code>java.util.TimeZone</code>.</p><p>In Camel 2.8.0 or older versions you would have to provide your custom <code>String</code> to <code>java.util.TimeZone</code> <a shape="rect" href="type-converter.html">Type Converter</a> to be able configure this from the endpoint uri.<br clear="none"> From Camel 2.8.1 onwards we have included such a <a shape="rect" href="type-converter.html">Type Converter</a> in the camel-core.</p><p></p><h3 id="Quartz-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="quartz2.html">Quartz2</a></li><li><a shape="rect" href="timer.html">Timer</a></li></ul></div>
         </td>
         <td valign="top">
           <div class="navigation">

Modified: websites/production/camel/content/quartz2.html
==============================================================================
--- websites/production/camel/content/quartz2.html (original)
+++ websites/production/camel/content/quartz2.html Fri Nov 21 14:19:16 2014
@@ -99,10 +99,7 @@ quartz2://groupName/timerName?options
 quartz2://groupName/timerName?cron=expression
 quartz2://timerName?cron=expression
 ]]></script>
-</div></div><p>The component uses either a <code>CronTrigger</code> or a <code>SimpleTrigger</code>. If no cron expression is provided, the component uses a simple trigger. If no <code>groupName</code> is provided, the quartz component uses the <code>Camel</code> group name.</p><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p><h3 id="Quartz2-Options">Options</h3><div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Parameter </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>cron</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>None</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies a <code>cron</code> expression (not compatible with the <code>trigger.*</code> or <code>job.*</code> options). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>trigger.repeatCount</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> SimpleTrigger: How many times should the timer repeat? </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>t
 rigger.repeatInterval</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>1000</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> SimpleTrigger: The amount of time in milliseconds between repeated triggers. Must enable <code>trigger.repeatCount</code> to use the simple trigger using this interval. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>job.name</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets the job name. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>job.<em>XXX</em></code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets the job option with the <code><em>XXX</em></code> setter name. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>trigger.<em>XXX
 </em></code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets the trigger option with the <code><em>XXX</em></code> setter name. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>stateful</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Uses a Quartz <code>@PersistJobDataAfterExecution</code> and <code>@DisallowConcurrentExecution</code> instead of the default job. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>fireNow</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If it is true will fire the trigger when the route is start when using SimpleTrigger.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>delete
 Job</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If set to true, then the trigger automatically delete when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>pauseJob</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If set to true, then the trigger automatically pauses when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to tr
 ue. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>durableJob</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.4/2.13</strong>: Whether or not the job should remain stored after it is orphaned (no triggers point to it). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>recoverableJob</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.4/2.13</strong>: Instructs the scheduler whether or not the job should be re-executed if a 'recovery' or 'fail-over' situation is<br clear="none">
- encountered. </p></td></tr></tbody></table></div>
-</div><p>For example, the following routing rule will fire two timer events to the <code>mock:results</code> endpoint:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>The component uses either a <code>CronTrigger</code> or a <code>SimpleTrigger</code>. If no cron expression is provided, the component uses a simple trigger. If no <code>groupName</code> is provided, the quartz component uses the <code>Camel</code> group name.</p><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p><h3 id="Quartz2-Options">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter</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>cron</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><em>None</em></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies a <code>cron</code> expre
 ssion (not compatible with the <code>trigger.*</code> or <code>job.*</code> options).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>trigger.repeatCount</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>SimpleTrigger: How many times should the timer repeat?</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>trigger.repeatInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>SimpleTrigger: The amount of time in milliseconds between repeated triggers. Must enable <code>trigger.repeatCount</code> to use the simple trigger using this interval.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>job.name</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" cl
 ass="confluenceTd"><p>Sets the job name.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>job.<em>XXX</em></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the job option with the <code><em>XXX</em></code> setter name.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>trigger.<em>XXX</em></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the trigger option with the <code><em>XXX</em></code> setter name.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>stateful</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses a Quartz <code>@PersistJobDataAfterExecution</code> and <code>@DisallowConcurrentExecution</code> inste
 ad of the default job.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>fireNow</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If it is true will fire the trigger when the route is start when using SimpleTrigger.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>deleteJob</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If set to true, then the trigger automatically delete when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>pauseJob</code></p></td><td colspan="1" rowspan=
 "1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If set to true, then the trigger automatically pauses when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>durableJob</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.4/2.13</strong>: Whether or not the job should remain stored after it is orphaned (no triggers point to it).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>recoverableJob</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confl
 uenceTd"><p><strong>Camel 2.12.4/2.13</strong>: Instructs the scheduler whether or not the job should be re-executed if a 'recovery' or 'fail-over' situation is<br clear="none"> encountered.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>usingFixedCamelContextName</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong><strong>Camel 2.15.0: </strong></strong><span style="line-height: 1.4285715;"><span style="line-height: 1.4285715;">If it is true, <span style="line-height: 1.4285715;">JobDataMap </span></span></span><span style="line-height: 1.4285715;">uses the CamelContext name directly to reference the camel context, </span><span style="line-height: 1.4285715;">if it is false, <span>JobDataMap </span><span>uses </span>use the CamelContext management name which could be changed during the deploy time.</span></td></tr></tbody></table></div></div><p>For example, the following
  routing rule will fire two timer events to the <code>mock:results</code> endpoint:</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(&quot;quartz2://myGroup/myTimerName?trigger.repeatInterval=2&amp;trigger.repeatCount=1&quot;).routeId(&quot;myRoute&quot;).to(&quot;mock:result&quot;);
 ]]></script>
 </div></div><p>When using <code>stateful=true</code>, the <a shape="rect" class="external-link" href="http://quartz-scheduler.org/api/2.0.0/org/quartz/JobDataMap.html" rel="nofollow">JobDataMap</a> is re-persisted after every execution of the job, thus preserving state for the next execution.</p>    <div class="aui-message hint shadowed information-macro">
@@ -112,16 +109,12 @@ quartz2://timerName?cron=expression
                             <p>If you run in OSGi such as Apache ServiceMix, or Apache Karaf, and have multiple bundles with Camel routes that start from <a shape="rect" href="quartz2.html">Quartz2</a> endpoints, then make sure if you assign<br clear="none"> an <code>id</code> to the &lt;camelContext&gt; that this id is unique, as this is required by the <code>QuartzScheduler</code> in the OSGi container. If you do not set any <code>id</code> on &lt;camelContext&gt; then<br clear="none"> a unique id is auto assigned, and there is no problem.</p>
                     </div>
     </div>
-<h3 id="Quartz2-Configuringquartz.propertiesfile">Configuring quartz.properties file</h3><p>By default Quartz will look for a <code>quartz.properties</code> file in the <code>org/quartz</code> directory of the classpath. If you are using WAR deployments this means just drop the quartz.properties in <code>WEB-INF/classes/org/quartz</code>.</p><p>However the Camel <a shape="rect" href="quartz2.html">Quartz2</a> component also allows you to configure properties:</p><div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Parameter </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>properties</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Properties</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> You can configure a <code>java.util.Properties</code> instance. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>propertiesFile</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td>
 <td colspan="1" rowspan="1" class="confluenceTd"><p> File name of the properties to load from the classpath </p></td></tr></tbody></table></div>
-</div><p>To do this you can configure this in Spring XML as follows</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="Quartz2-Configuringquartz.propertiesfile">Configuring quartz.properties file</h3><p>By default Quartz will look for a <code>quartz.properties</code> file in the <code>org/quartz</code> directory of the classpath. If you are using WAR deployments this means just drop the quartz.properties in <code>WEB-INF/classes/org/quartz</code>.</p><p>However the Camel <a shape="rect" href="quartz2.html">Quartz2</a> component also allows you to configure properties:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null
 </code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Properties</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can configure a <code>java.util.Properties</code> instance.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>propertiesFile</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>File name of the properties to load from the classpath</p></td></tr></tbody></table></div></div><p>To do this you can configure this in Spring XML as follows</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[&lt;bean id=&quot;quartz&quot; class=&quot;org.apache.camel.component.quartz2.QuartzComponent&quot;&gt;
     &lt;property name=&quot;propertiesFile&quot; value=&quot;com/mycompany/myquartz.properties&quot;/&gt;
 &lt;/bean&gt;
 ]]></script>
-</div></div><h3 id="Quartz2-EnablingQuartzschedulerinJMX">Enabling Quartz scheduler in JMX</h3><p>You need to configure the quartz scheduler properties to enable JMX.<br clear="none"> That is typically setting the option <code>"org.quartz.scheduler.jmx.export"</code> to a <code>true</code> value in the configuration file.</p><p>From Camel 2.13 onwards Camel will automatic set this option to true, unless explicit disabled.</p><h3 id="Quartz2-StartingtheQuartzscheduler">Starting the Quartz scheduler</h3><p>The <a shape="rect" href="quartz2.html">Quartz2</a> component offers an option to let the Quartz scheduler be started delayed, or not auto started at all.</p><div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Parameter </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>startDelayedSeconds</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Seconds to wait before starting the quartz scheduler. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>autoStartScheduler</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td co
 lspan="1" rowspan="1" class="confluenceTd"><p> Whether or not the scheduler should be auto started. </p></td></tr></tbody></table></div>
-</div><p>To do this you can configure this in Spring XML as follows</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="Quartz2-EnablingQuartzschedulerinJMX">Enabling Quartz scheduler in JMX</h3><p>You need to configure the quartz scheduler properties to enable JMX.<br clear="none"> That is typically setting the option <code>"org.quartz.scheduler.jmx.export"</code> to a <code>true</code> value in the configuration file.</p><p>From Camel 2.13 onwards Camel will automatic set this option to true, unless explicit disabled.</p><h3 id="Quartz2-StartingtheQuartzscheduler">Starting the Quartz scheduler</h3><p>The <a shape="rect" href="quartz2.html">Quartz2</a> component offers an option to let the Quartz scheduler be started delayed, or not auto started at all.</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1
 " class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>startDelayedSeconds</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Seconds to wait before starting the quartz scheduler.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>autoStartScheduler</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether or not the scheduler should be auto started.</p></td></tr></tbody></table></div></div><p>To do this you can configure this in Spring XML as follows</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[&lt;bean id=&quot;quartz2&quot; class=&quot;org.apache.camel.component.quartz2.QuartzComponent&quot;&gt;
     &lt;property name=&quot;startDelayedSeconds&quot; value=&quot;5&quot;/&gt;
 &lt;/bean&gt;
@@ -132,18 +125,14 @@ quartz2://timerName?cron=expression
 </div></div><p>which is equivalent to using the cron expression</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[0 0/5 12-18 ? * MON-FRI
 ]]></script>
-</div></div><p>The following table shows the URI character encodings we use to preserve valid URI syntax:</p><div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>URI Character</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Cron character</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>+</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>Space</em> </p></td></tr></tbody></table></div>
-</div><h3 id="Quartz2-Specifyingtimezone">Specifying time zone</h3><p>The Quartz Scheduler allows you to configure time zone per trigger. For example to use a timezone of your country, then you can do as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>The following table shows the URI character encodings we use to preserve valid URI syntax:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>URI Character</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Cron character</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>+</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><em>Space</em></p></td></tr></tbody></table></div></div><h3 id="Quartz2-Specifyingtimezone">Specifying time zone</h3><p>The Quartz Scheduler allows you to configure time zone per trigger. For example to use a timezone of your country, then you can do as follows:</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[quartz2://groupName/timerName?cron=0+0/5+12-18+?+*+MON-FRI&amp;trigger.timeZone=Europe/Stockholm
 ]]></script>
 </div></div><p>The timeZone value is the values accepted by <code>java.util.TimeZone</code>.</p><h2 id="Quartz2-UsingQuartzScheduledPollConsumerScheduler">Using QuartzScheduledPollConsumerScheduler</h2><p>The <a shape="rect" href="quartz2.html">Quartz2</a> component provides a <a shape="rect" href="polling-consumer.html">Polling Consumer</a> scheduler which allows to use cron based scheduling for <a shape="rect" href="polling-consumer.html">Polling Consumer</a> such as the <a shape="rect" href="file2.html">File</a> and <a shape="rect" href="ftp2.html">FTP</a> consumers.</p><p>For example to use a cron based expression to poll for files every 2nd second, then a Camel route can be define simply as:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[    from(&quot;file:inbox?scheduler=quartz2&amp;scheduler.cron=0/2+*+*+*+*+?&quot;)
        .to(&quot;bean:process&quot;);
 ]]></script>
-</div></div><p>Notice we define the <code>scheduler=quartz2</code> to instruct Camel to use the <a shape="rect" href="quartz2.html">Quartz2</a> based scheduler. Then we use <code>scheduler.xxx</code> options to configure the scheduler. The <a shape="rect" href="quartz2.html">Quartz2</a> scheduler requires the cron option to be set.</p><p>The following options is supported:</p><div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Parameter </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>quartzScheduler</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>org.quartz.Scheduler</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a custom Quartz scheduler. If none configure then the shared scheduler from the <a shape="rect" href="quartz2.html">Quartz2</a> component is used. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cron</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</co
 de> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Mandatory</strong>: To define the cron expression for triggering the polls. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>triggerId</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To specify the trigger id. If none provided then an UUID is generated and used. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>triggerGroup</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>QuartzScheduledPollConsumerScheduler</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To specify the
  trigger group. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>timeZone</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Default</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>TimeZone</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The time zone to use for the CRON trigger. </p></td></tr></tbody></table></div>
-</div><p><strong>Important:</strong> Remember configuring these options from the endpoint <a shape="rect" href="uris.html">URIs</a> must be prefixed with <code>scheduler.</code>.<br clear="none"> For example to configure the trigger id and group:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Notice we define the <code>scheduler=quartz2</code> to instruct Camel to use the <a shape="rect" href="quartz2.html">Quartz2</a> based scheduler. Then we use <code>scheduler.xxx</code> options to configure the scheduler. The <a shape="rect" href="quartz2.html">Quartz2</a> scheduler requires the cron option to be set.</p><p>The following options is supported:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>quartzScheduler</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>org.quart
 z.Scheduler</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To use a custom Quartz scheduler. If none configure then the shared scheduler from the <a shape="rect" href="quartz2.html">Quartz2</a> component is used.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>cron</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Mandatory</strong>: To define the cron expression for triggering the polls.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>triggerId</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To specify the trigger id. If none provided then an UUID is gener
 ated and used.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>triggerGroup</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>QuartzScheduledPollConsumerScheduler</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To specify the trigger group.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>timeZone</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Default</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>TimeZone</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The time zone to use for the CRON trigger.</p></td></tr></tbody></table></div></div><p><strong>Important:</strong> Remember configuring these options from the endpoint <a shape="rect" href="uris.html">URIs</a> must be prefixed with <code>scheduler.</code>.<br clear="none"> For example to conf
 igure the trigger id and group:</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(&quot;file:inbox?scheduler=quartz2&amp;scheduler.cron=0/2+*+*+*+*+?&amp;scheduler.triggerId=myId&amp;scheduler.triggerGroup=myGroup&quot;)
        .to(&quot;bean:process&quot;);
 ]]></script>



Mime
View raw message