camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r940979 [2/3] - in /websites/production/camel/content: ./ cache/
Date Sat, 21 Feb 2015 15:18:33 GMT
Modified: websites/production/camel/content/camel-2150-release.html
==============================================================================
--- websites/production/camel/content/camel-2150-release.html (original)
+++ websites/production/camel/content/camel-2150-release.html Sat Feb 21 15:18:33 2015
@@ -84,7 +84,7 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h1 id="Camel2.15.0Release-Camel2.15.0release(currentlyinprogress)">Camel&#160;2.15.0 release (currently in progress)</h1><div style="padding-right:20px;float:left;margin-left:-20px;"><p><img class="confluence-embedded-image confluence-external-resource" src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png" data-image-src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png"></p></div><div style="min-height:200px">&#160;</div><h2 id="Camel2.15.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to the 2.15.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p><ul><li><span>Component, data format, language and eip documentation now included in the built component JARs. And Java API and JMX API to access that documentation. And APIs to explain an endpoint uri, eip configuration and what all those configured options mean. In other words the same level of complete d
 ocumentation of your Camel apps at both design and runtime, accessible from Java / JMX and tooling.</span></li><li><span>Component, data format, language and eip can now have&#160;associated&#160;label(s) which are used for grouping components into: core, database, messaging, http, rest, etc.</span></li><li><span>The XML DSL schema now include documentation</span></li><li><span>Provide Configurer for user to configure the CXF conduit and CXF destination from Java code</span></li><li><span><span>Added a <code>DelegateEndpoint</code>&#160;interface into Camel API</span></span></li><li>Support to setup the SslContextParameters in the <a shape="rect" href="restlet.html">camel-restlet</a> component</li><li>Java DSL - Should support nested choice in doTry .. doCatch</li><li><a shape="rect" href="mongodb.html">MongoDb</a> component now <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-7996">stores OIDs</a>&#160;of the inserted records in the message he
 ader</li><li><a shape="rect" href="recipient-list.html">Recipient List</a> now supports specifying custom&#160;<a shape="rect" href="exchange-pattern.html">Exchange Pattern</a> in the endpoint ur's</li><li><a shape="rect" href="type-converter.html">Type Converter</a> to enum's is now case insensitive, so you can convert safely level=info to an enum with name Level.INFO etc.</li><li><a shape="rect" href="xslt.html">XSLT</a> and&#160;<a shape="rect" href="https://cwiki.apache.org/confluence/display/SM/Validation">Validation</a> components now provides all their endpoint configurations in the endpoint, and not only in the component, making these components like any other components.</li><li>Made the <a shape="rect" href="karaf.html">Camel Karaf Commands</a> reusable by moving common code into a&#160;<code>camel-commands-core</code> module that SPI can extend and plugin Camel commands for other environments.</li><li>Further hardening of the&#160;<a shape="rect" href="sjms.html">SJMS</a>
 &#160;component.</li><li><a shape="rect" href="rest-dsl.html">Rest DSL</a> with embedded routes now supports <a shape="rect" href="exception-clause.html">onException</a>, <a shape="rect" href="intercept.html">intercept</a> etc in use for those embedded routes, just like any regular routes.&#160;</li><li><a shape="rect" href="rest-dsl.html">Rest DSL</a> now by default uses custom error message as-is without attempting to binding output (requires a HTTP error code of 300+ is set as a header)</li><li>Camel&#160;<a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a> now supports specifying a default value together with the key to lookup.</li><li>Camel&#160;<a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a> now supports not having to define a PropertiesComponent if all the placeholder keys has default values which are to be used (less configuration needed in those situations).</li><li>Camel&#160;<a shape="rect" href="using-pro
 pertyplaceholder.html">Using PropertyPlaceholder</a> now supports 3rd party functions to lookup the property values, this allow end users to implement their own logic - we provide 3 out of the box functions to lookup values from OS environment variable, JVM system properties, or the service name idiom.</li><li><a shape="rect" href="rabbitmq.html">RabbitMQ</a> now pools Channels for the producer to avoid sharing same Channel among concurrent producers which are not recommended by RabbitMQ client.</li><li>Camel commands is now reusable outside Apache Karaf as a base by the&#160;<code>commands-core</code> module.</li><li>Camel commands using <a shape="rect" class="external-link" href="http://www.jolokia.org/" rel="nofollow">Jolokia</a> for remote communication by the&#160;<code>commands-jolokia</code> module.</li><li>More minor processors such as setHeader, removeHeader, removeHeaders and ditto for properties is now also enlisted in JMX under processors.</li><li>Optimized usage of type
  conversion during routing reducing the number of attempts needed.</li><li>Optimized CaseInsentiveMap used as message headers to use a single map instead of two and yield less memory overhead and performance</li><li>Asynchronous routing engine that are forced to block threads now exposes this using a <a shape="rect" href="asyncprocessorawaitmanager.html">manager</a> that offers runtime insight using JMX. And as well attempts to free blocked threads during graceful shutdown, to avoid any threads hanging in the JVM.</li><li><a shape="rect" href="swagger.html">Swagger</a> now supports any kind of runtime environment, as only JMX being enabled is required.</li><li><a shape="rect" href="xml-security-component.html">XML Security component</a> supports now&#160;&#160;XAdES-BES/EPES&#160;in the signer endpoint.</li><li><a shape="rect" href="hl7.html">HL7</a> MLLP codec now supports&#160;<a shape="rect" href="netty4.html">Netty4</a> based transport.</li><li>Inflight repository now allows to 
 browse the current inflight exchanges to obtain information where these exchanges are inflight and for how long. Expose this information in JMX and Camel commands as well.</li><li><a shape="rect" href="graceful-shutdown.html">Graceful Shutdown</a> now logs information about the inflight exchanges that are still present during shutdown and a timeout was hit.</li><li><a shape="rect" href="message-history.html">Message History</a> which dumps&#160;Exchange information not supports the&#160;<span style="color: rgb(0,0,0);"><a shape="rect" href="how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.html">Exchange.LOG_DEBUG_BODY_MAX_CHARS</a> option to limit the max chars outputted in the logs.</span></li><li><code>DefaultClassLoader</code> now fallback and use the application context classloader that may have been set on&#160;<code>CamelContext</code> to better be able to load classes/resources from classpath in different runtime environments.<span style="color: rgb(0,0,0);"><b
 r clear="none"></span></li><li><a shape="rect" href="camel-jmx.html">Camel JMX</a> now includes current inflight exchanges at processor level, which means we can have a complete breakdown where exchanges are, and as well from the improved&#160;<code>InflightRegistry</code> which has APi and JMX api to browse the current inflight with details of the exchange and processing times etc.</li><li>Support for Jetty 9 using the new&#160;<code>camel-component-jetty9</code> module.</li><li>The&#160;<code>EndpointRegistry</code> now stores endpoints in two caches; a static unbounded cache to keep endpoints for their lifetime, and a dynamic limited cache to keep only the recently used endpoints.&#160;</li><li><a shape="rect" href="endpoint.html">Endpoint</a>'s used by routes are kept in the static cache of the&#160;<code>EndpointRegistry</code> as long as the lifetime of the routes.</li><li>Removing a route now also remove its static&#160;<a shape="rect" href="endpoint.html">Endpoint</a>'s from
  the&#160;<code>EndpointRegistry</code> (if those endpoints are not shared and used by other routes). Mind that any dynamic endpoint created during routing from dynamic&#160;<a shape="rect" href="eip.html">EIP</a>s such as recipient list, routing slip, dynamic router etc, are not removed from the <code>EndpointRegistry</code>&#160;when the route is removed.</li><li><a shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> now logs a WARN if a new exception occurred while it was attempting to process the dead letter message. The new exception will by default be handled so the&#160;<a shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> always complete succesfull. The new option&#160;<span>deadLetterHandleNewException</span><span>&#160;can be set to&#160;<code>false</code> to turn this off.</span></li><li><span><a shape="rect" href="groovy.html">GroovyShell</a> creation process can now be <a shape="rect" class="external-link" href="https://issues.apache.o
 rg/jira/browse/CAMEL-8259">customized</a> using <code>GroovyShellFactory</code> SPI interface.</span></li><li><a shape="rect" href="how-do-i-configure-endpoints.html">Configuring endpoint uris in XML DSL</a> now allow to specify the uri attribute using multiple lines; this can make it more readable when having very long uris. Notice only the uri attributes support this.</li><li><a shape="rect" href="how-do-i-configure-endpoints.html">Configuring endpoint uris in XML DSL</a>&#160;now allow to specify endpoint options using &lt;property&gt; &#160;bean style in the &lt;endpoint&gt; configuration;&#160;&#160;this can make it more readable when having very long uris.&#160;</li><li>Using custom Jackson modules is easier with the Jackson&#160;<a shape="rect" href="json.html">JSON</a>&#160;data format.</li><li>Some HTTP producer now allows GET operations with message body (though a bit unusual to do)</li></ul><h3 id="Camel2.15.0Release-Fixedissues">Fixed issues</h3><ul><li>Fixed processors 
 was not enlisted in JMX when routes was transacted.</li><li>Fixed the NullPointerException when using CXF endpoint with enrich</li><li>Fixed the&#160;endpointProperty of&#160;restConfiguration doesn't work issue</li><li>Fixed the issue that&#160;CircuitBreakerLoadBalancer fails on async processors</li><li>Fixed&#160;MyBatis consumer <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-8011">ignoring maxMessagesPerPoll</a> option</li><li>Fixed potential issue with&#160;pollEnrich not triggering error handler if an exception was thrown in the polling.</li><li>Fixed a memory leak if using&#160;<a shape="rect" href="dynamic-router.html">Dynamic Router</a> that loops many times, and uses&#160;any of&#160;<code>convertBodyTo</code> or&#160;<code>setBody</code> or&#160;<code>transform</code> in the loop, causing memory to stack up until the Exchange is done.</li><li>Fixed and improved how&#160;<a shape="rect" href="bean.html">Bean</a>&#160;component and&#
 160;<a shape="rect" href="simple.html">Simple</a>&#160;language invoking beans detect methods that are overridden, and able to filter and apply this as a single method, to be invoked. Avoids AmbiguousMethodCallException&#160;being thrown.</li><li>Fixed a thread leak if restarting routes using stop/start and the routes is a scheduled poll consumer, such as file/ftp&#160;components.</li><li>Using ?exchangePattern=InOnly or InOut in endpoint uris now take precedence as the pattern in use when sending to the endpoint, using to/recipient list.</li><li><a shape="rect" href="mail.html">Mail</a>&#160;component no longer includes headers starting with&#160;<code>Camel</code> in their keys, as those are consider internal headers and should not be included in the sent emails.</li><li>Fixed readLock=fileLock on the file component</li><li>Fixed&#160;<a shape="rect" href="stomp.html">Stomp</a>&#160;not detecting failure when sending, but was assuming a send always succeeded</li><li>Fixed&#160;<a 
 shape="rect" href="mqtt.html">MQTT</a>&#160;sending to broker being more resilient and automatic ensure re-connection when connection failures</li><li>Fixed sending to FTP may cause the producer to hang in an endless reconnection attempt if the socket connection is dead. (Use soTimeout=10000 or some positive value to potential mitigate this in older releases).<br clear="none"><br clear="none"></li></ul><h3 id="Camel2.15.0Release-New">New <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a></h3><h3 id="Camel2.15.0Release-New.1">New <a shape="rect" href="components.html">Components</a></h3><ul><li><a shape="rect" href="beanstalk.html">camel-beanstalk</a> - for working with Amazon Beanstalk jobs.</li><li>came-cassandraql -&#160;Cassandra CQL3 support</li><li><code>camel-chunk</code> - for templating with Chunk engine.</li><li><a shape="rect" href="docker.html">camel-docker</a> - to communicate with Docker.</li><li>camel-dozer - Now also as a c
 omponent to convert messages using the Dozer type conversion framework</li><li>camel-github - for integrating with github</li><li>camel-google-calendar -&#160;provides access to&#160;<a shape="rect" class="external-link" href="http://google.com/calendar" rel="nofollow">Google Calendar</a>&#160;via the&#160;<a shape="rect" class="external-link" href="https://developers.google.com/google-apps/calendar/v3/reference/" rel="nofollow">Google Calendar Web APIs</a>.</li><li>camel-google-mail -&#160;provides access to&#160;<a shape="rect" class="external-link" href="http://gmail.com/" rel="nofollow">Gmail</a>&#160;via the&#160;<a shape="rect" class="external-link" href="https://developers.google.com/gmail/api/v1/reference/" rel="nofollow">Google Mail Web APIs</a>.</li><li><a shape="rect" href="hipchat.html">camel-hipchat</a> - to integrate with the Hipchat service</li><li>camel-pgevent -&#160;Component for sending/receiving notifications in PostgreSQL via the pgjdbc-ng driver</li><li>camel-j
 ira - for integrating with JIRA issue tracker</li><li><a shape="rect" href="kura.html">camel-kura</a> - for deploying Camel OSGi routes into <a shape="rect" class="external-link" href="https://eclipse.org/kura/" rel="nofollow">Eclipse Kura</a> M2M container.</li><li>camel-scr - for using Camel with <a shape="rect" class="external-link" href="http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html">SCR</a>&#160;(OSGi declarative services) on OSGi containers such as Apache Karaf</li><li><a shape="rect" href="spring-boot.html">camel-spring-boot</a> - for using Camel with Spring Boot</li><li>camel-test-spring40 - for testing with Spring 4.0.x. camel-test-spring is for Spring 4.1.x onwards.</li></ul><h3 id="Camel2.15.0Release-NewDSL">New DSL</h3><ul><li>Added <strong>removeProperties</strong> to remove the properties from exchange.</li></ul><h3 id="Camel2.15.0Release-NewAnnotations">New Annotations</h3><h3 id="Camel2.15.0Release-NewDataFormats
 ">New <a shape="rect" href="data-format.html">Data Formats</a></h3><ul><li>camel-univocity-parsers</li></ul><h3 id="Camel2.15.0Release-New.2">New <a shape="rect" href="languages.html">Languages</a></h3><h3 id="Camel2.15.0Release-New.3">New <a shape="rect" href="examples.html">Examples</a></h3><h3 id="Camel2.15.0Release-New.4">New <a shape="rect" href="tutorials.html">Tutorials</a></h3><h2 id="Camel2.15.0Release-KnownIssues">Known Issues</h2><h2 id="Camel2.15.0Release-DependencyUpgrades"><span>Dependency Upgrades</span></h2><ul><li>AWS-Java-SDK 1.8.3 to 1.8.9.1</li><li>Codahale Metrics 3.0 to 3.1</li><li>CXF 3.0.2 to 3.0.3</li><li>Hazelcast 3.3.2 to 3.4</li><li>JAXB 2.2.7 to 2.2.11</li><li>JRuby 1.7.16 to 1.7.18</li><li>Guava 17.0 to 18.0</li><li>Jsch 0.1.50 to 0.1.51</li><li>JsonPath 1.1.0 to 1.2.0</li><li>Spring 4.0.7.RELEASE to 4.1.4.RELEASE</li><li>Spring Security 3.1.7.RELEASE to 3.2.5.RELEASE</li><li>RX Java 0.20 to 1.0.5</li><li>... and many other upgrades</li></ul><h2 id="Cam
 el2.15.0Release-Importantchangestoconsiderwhenupgrading">Important changes to consider when upgrading</h2><ul><li>Spring 4.1.x is now the default out of the box Spring version.</li><li><span style="color: rgb(0,0,0);">Unit testing with Spring 4.0.x requires using camel-test-spring40, as camel-test-spring is for Spring 4.1 or better.</span></li><li><span style="color: rgb(0,0,0);">Remember to add&#160;<code class="java color1">@BootstrapWith</code><code class="java plain">(CamelTestContextBootstrapper.</code><code class="java keyword">class</code><code class="java plain">)</code>&#160;if upgrading from Spring 3.x or 4.0.x to Spring 4.1 onwards, and using the camel-test-spring module.</span></li><li><a shape="rect" href="xslt.html">XSLT</a>&#160;component now require configuring&#160;<code>transformerFactory</code> using&#160;<a shape="rect" href="uris.html">URIs</a> with the #syntax to refer to a bean. Just like any other component would do.</li><li>Slight refactor in&#160;<code>came
 l-metrics</code> component which may affect users who are using the java endpoint types instead of configuring using uris</li><li><code>camel-csv</code> upgraded to Commons CSV 1.x which has a different API than the old 0.x version. End users may need to adjust their code.</li><li><code>camel-sjms</code> has been refactored a bit to further harden this component.&#160;End users may need to adjust their code.</li><li>The <a shape="rect" href="simple.html">simple</a> function properties:locations:key has been renamed to properties-location:locations:key, as it would clash with the new functionality to specify a default value after the key name, eg properties:key:default</li><li>Removed the backlog tracer commands from the Karaf Camel commands as they are not suitable for a CLI environment</li><li>The need for runtime specific servlets in <a shape="rect" href="swagger.html">Swagger</a>&#160;has been removed, and instead just use the default servlet which is provided out of the box.&#16
 0;</li><li><code>org.apache.camel.spi.InflightRepository</code> now includes additional methods for browsing in-flight exchanges.</li><li>Using ?exchangePattern=InOnly or InOut in endpoint uris now take precedence as the pattern in use when sending to the endpoint, using to/recipient list.</li><li><code>DefaultClassLoader</code> now fallback and use the application context classloader that may have been set on&#160;<code>CamelContext</code> to better be able to load classes/resources from classpath in different runtime environments.</li><li><a shape="rect" href="mail.html">Mail</a>&#160;component no longer includes headers starting with&#160;<code>Camel</code> in their keys, as those are consider internal headers and should not be included in the sent emails.</li><li>Removing a route now also remove its static&#160;<a shape="rect" href="endpoint.html">Endpoint</a>'s from the&#160;<code>EndpointRegistry</code> (if those endpoints are not shared and used by other routes). Mind that an
 y dynamic endpoint created during routing from dynamic&#160;<a shape="rect" href="eip.html">EIP</a>s such as recipient list, routing slip, dynamic router etc, are not removed from the <code>EndpointRegistry</code>&#160;when the route is removed.</li><li>All boolean isFoo methods on the model classes has been removed to ensure the model has consistent java bean getter/setter style with exactly one getter and one setter of the same type.</li><li>The exchange property language has been renamed from property to exchangeProperty&#160;<span>to avoid ambiguity, confusion and clash with properties as a general term. So use exchangeProperty instead of property.</span></li><li>camel-box now uses the CamelBox.folderId as a header instead of exchange property to use control the folder id when uploading to box</li><li>The delay option in <a shape="rect" href="snmp.html">SNMP</a> has changed from using seconds to millis as time unit.</li><li>Routing starting from a&#160;<a shape="rect" href="bean
 .html">Bean</a>&#160;endpoint is not supported (which wasnt really intended anyway), instead start with a scheduler and use to bean instead.<br clear="none"><br clear="none"></li></ul><h2 id="Camel2.15.0Release-GettingtheDistributions">Getting the Distributions</h2><h3 id="Camel2.15.0Release-BinaryDistributions">Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.15.0/apache-camel-x.y.x.zip">apache-camel-2.15.0.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceT
 d"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/camel/apache-camel/2.15.0/apache-camel-x.y.x.zip.asc">apache-camel-2.15.0.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.15.0/apache-camel-x.y.x.tar.gz">apache-camel-2.15.0.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/camel/apache-camel/2.15.0/apache-camel-x.y.x.tar.gz.asc">apache-camel-2.15.0.tar.gz.asc</a></p></td></tr></tbody></table></div>    <div class="aui-message hint shadowed information-macro">
+<div class="wiki-content maincontent"><h1 id="Camel2.15.0Release-Camel2.15.0release(currentlyinprogress)">Camel&#160;2.15.0 release (currently in progress)</h1><div style="padding-right:20px;float:left;margin-left:-20px;"><p><img class="confluence-embedded-image confluence-external-resource" src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png" data-image-src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png"></p></div><div style="min-height:200px">&#160;</div><h2 id="Camel2.15.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to the 2.15.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p><ul><li><span>Component, data format, language and eip documentation now included in the built component JARs. And Java API and JMX API to access that documentation. And APIs to explain an endpoint uri, eip configuration and what all those configured options mean. In other words the same level of complete d
 ocumentation of your Camel apps at both design and runtime, accessible from Java / JMX and tooling.</span></li><li><span>Component, data format, language and eip can now have&#160;associated&#160;label(s) which are used for grouping components into: core, database, messaging, http, rest, etc.</span></li><li><span>The XML DSL schema now include documentation</span></li><li><span>Provide Configurer for user to configure the CXF conduit and CXF destination from Java code</span></li><li><span><span>Added a <code>DelegateEndpoint</code>&#160;interface into Camel API</span></span></li><li>Support to setup the SslContextParameters in the <a shape="rect" href="restlet.html">camel-restlet</a> component</li><li>Java DSL - Should support nested choice in doTry .. doCatch</li><li><a shape="rect" href="mongodb.html">MongoDb</a> component now <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-7996">stores OIDs</a>&#160;of the inserted records in the message he
 ader</li><li><a shape="rect" href="recipient-list.html">Recipient List</a> now supports specifying custom&#160;<a shape="rect" href="exchange-pattern.html">Exchange Pattern</a> in the endpoint ur's</li><li><a shape="rect" href="type-converter.html">Type Converter</a> to enum's is now case insensitive, so you can convert safely level=info to an enum with name Level.INFO etc.</li><li><a shape="rect" href="xslt.html">XSLT</a> and&#160;<a shape="rect" href="https://cwiki.apache.org/confluence/display/SM/Validation">Validation</a> components now provides all their endpoint configurations in the endpoint, and not only in the component, making these components like any other components.</li><li>Made the <a shape="rect" href="karaf.html">Camel Karaf Commands</a> reusable by moving common code into a&#160;<code>camel-commands-core</code> module that SPI can extend and plugin Camel commands for other environments.</li><li>Further hardening of the&#160;<a shape="rect" href="sjms.html">SJMS</a>
 &#160;component.</li><li><a shape="rect" href="rest-dsl.html">Rest DSL</a> with embedded routes now supports <a shape="rect" href="exception-clause.html">onException</a>, <a shape="rect" href="intercept.html">intercept</a> etc in use for those embedded routes, just like any regular routes.&#160;</li><li><a shape="rect" href="rest-dsl.html">Rest DSL</a> now by default uses custom error message as-is without attempting to binding output (requires a HTTP error code of 300+ is set as a header)</li><li>Camel&#160;<a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a> now supports specifying a default value together with the key to lookup.</li><li>Camel&#160;<a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a> now supports not having to define a PropertiesComponent if all the placeholder keys has default values which are to be used (less configuration needed in those situations).</li><li>Camel&#160;<a shape="rect" href="using-pro
 pertyplaceholder.html">Using PropertyPlaceholder</a> now supports 3rd party functions to lookup the property values, this allow end users to implement their own logic - we provide 3 out of the box functions to lookup values from OS environment variable, JVM system properties, or the service name idiom.</li><li><a shape="rect" href="rabbitmq.html">RabbitMQ</a> now pools Channels for the producer to avoid sharing same Channel among concurrent producers which are not recommended by RabbitMQ client.</li><li>Camel commands is now reusable outside Apache Karaf as a base by the&#160;<code>commands-core</code> module.</li><li>Camel commands using <a shape="rect" class="external-link" href="http://www.jolokia.org/" rel="nofollow">Jolokia</a> for remote communication by the&#160;<code>commands-jolokia</code> module.</li><li>More minor processors such as setHeader, removeHeader, removeHeaders and ditto for properties is now also enlisted in JMX under processors.</li><li>Optimized usage of type
  conversion during routing reducing the number of attempts needed.</li><li>Optimized CaseInsentiveMap used as message headers to use a single map instead of two and yield less memory overhead and performance</li><li>Asynchronous routing engine that are forced to block threads now exposes this using a <a shape="rect" href="asyncprocessorawaitmanager.html">manager</a> that offers runtime insight using JMX. And as well attempts to free blocked threads during graceful shutdown, to avoid any threads hanging in the JVM.</li><li><a shape="rect" href="swagger.html">Swagger</a> now supports any kind of runtime environment, as only JMX being enabled is required.</li><li><a shape="rect" href="xml-security-component.html">XML Security component</a> supports now&#160;&#160;XAdES-BES/EPES&#160;in the signer endpoint.</li><li><a shape="rect" href="hl7.html">HL7</a> MLLP codec now supports&#160;<a shape="rect" href="netty4.html">Netty4</a> based transport.</li><li>Inflight repository now allows to 
 browse the current inflight exchanges to obtain information where these exchanges are inflight and for how long. Expose this information in JMX and Camel commands as well.</li><li><a shape="rect" href="graceful-shutdown.html">Graceful Shutdown</a> now logs information about the inflight exchanges that are still present during shutdown and a timeout was hit.</li><li><a shape="rect" href="message-history.html">Message History</a> which dumps&#160;Exchange information not supports the&#160;<span style="color: rgb(0,0,0);"><a shape="rect" href="how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.html">Exchange.LOG_DEBUG_BODY_MAX_CHARS</a> option to limit the max chars outputted in the logs.</span></li><li><code>DefaultClassLoader</code> now fallback and use the application context classloader that may have been set on&#160;<code>CamelContext</code> to better be able to load classes/resources from classpath in different runtime environments.<span style="color: rgb(0,0,0);"><b
 r clear="none"></span></li><li><a shape="rect" href="camel-jmx.html">Camel JMX</a> now includes current inflight exchanges at processor level, which means we can have a complete breakdown where exchanges are, and as well from the improved&#160;<code>InflightRegistry</code> which has APi and JMX api to browse the current inflight with details of the exchange and processing times etc.</li><li>Support for Jetty 9 using the new&#160;<code>camel-component-jetty9</code> module.</li><li>The&#160;<code>EndpointRegistry</code> now stores endpoints in two caches; a static unbounded cache to keep endpoints for their lifetime, and a dynamic limited cache to keep only the recently used endpoints.&#160;</li><li><a shape="rect" href="endpoint.html">Endpoint</a>'s used by routes are kept in the static cache of the&#160;<code>EndpointRegistry</code> as long as the lifetime of the routes.</li><li>Removing a route now also remove its static&#160;<a shape="rect" href="endpoint.html">Endpoint</a>'s from
  the&#160;<code>EndpointRegistry</code> (if those endpoints are not shared and used by other routes). Mind that any dynamic endpoint created during routing from dynamic&#160;<a shape="rect" href="eip.html">EIP</a>s such as recipient list, routing slip, dynamic router etc, are not removed from the <code>EndpointRegistry</code>&#160;when the route is removed.</li><li><a shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> now logs a WARN if a new exception occurred while it was attempting to process the dead letter message. The new exception will by default be handled so the&#160;<a shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> always complete succesfull. The new option&#160;<span>deadLetterHandleNewException</span><span>&#160;can be set to&#160;<code>false</code> to turn this off.</span></li><li><span><a shape="rect" href="groovy.html">GroovyShell</a> creation process can now be <a shape="rect" class="external-link" href="https://issues.apache.o
 rg/jira/browse/CAMEL-8259">customized</a> using <code>GroovyShellFactory</code> SPI interface.</span></li><li><a shape="rect" href="how-do-i-configure-endpoints.html">Configuring endpoint uris in XML DSL</a> now allow to specify the uri attribute using multiple lines; this can make it more readable when having very long uris. Notice only the uri attributes support this.</li><li><a shape="rect" href="how-do-i-configure-endpoints.html">Configuring endpoint uris in XML DSL</a>&#160;now allow to specify endpoint options using &lt;property&gt; &#160;bean style in the &lt;endpoint&gt; configuration;&#160;&#160;this can make it more readable when having very long uris.&#160;</li><li>Using custom Jackson modules is easier with the Jackson&#160;<a shape="rect" href="json.html">JSON</a>&#160;data format.</li><li>Some HTTP producer now allows GET operations with message body (though a bit unusual to do)</li></ul><h3 id="Camel2.15.0Release-Fixedissues">Fixed issues</h3><ul><li>Fixed processors 
 was not enlisted in JMX when routes was transacted.</li><li>Fixed the NullPointerException when using CXF endpoint with enrich</li><li>Fixed the&#160;endpointProperty of&#160;restConfiguration doesn't work issue</li><li>Fixed the issue that&#160;CircuitBreakerLoadBalancer fails on async processors</li><li>Fixed&#160;MyBatis consumer <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-8011">ignoring maxMessagesPerPoll</a> option</li><li>Fixed potential issue with&#160;pollEnrich not triggering error handler if an exception was thrown in the polling.</li><li>Fixed a memory leak if using&#160;<a shape="rect" href="dynamic-router.html">Dynamic Router</a> that loops many times, and uses&#160;any of&#160;<code>convertBodyTo</code> or&#160;<code>setBody</code> or&#160;<code>transform</code> in the loop, causing memory to stack up until the Exchange is done.</li><li>Fixed and improved how&#160;<a shape="rect" href="bean.html">Bean</a>&#160;component and&#
 160;<a shape="rect" href="simple.html">Simple</a>&#160;language invoking beans detect methods that are overridden, and able to filter and apply this as a single method, to be invoked. Avoids AmbiguousMethodCallException&#160;being thrown.</li><li>Fixed a thread leak if restarting routes using stop/start and the routes is a scheduled poll consumer, such as file/ftp&#160;components.</li><li>Using ?exchangePattern=InOnly or InOut in endpoint uris now take precedence as the pattern in use when sending to the endpoint, using to/recipient list.</li><li><a shape="rect" href="mail.html">Mail</a>&#160;component no longer includes headers starting with&#160;<code>Camel</code> in their keys, as those are consider internal headers and should not be included in the sent emails.</li><li>Fixed readLock=fileLock on the file component</li><li>Fixed&#160;<a shape="rect" href="stomp.html">Stomp</a>&#160;not detecting failure when sending, but was assuming a send always succeeded</li><li>Fixed&#160;<a 
 shape="rect" href="mqtt.html">MQTT</a>&#160;sending to broker being more resilient and automatic ensure re-connection when connection failures</li><li>Fixed sending to FTP may cause the producer to hang in an endless reconnection attempt if the socket connection is dead. (Use soTimeout=10000 or some positive value to potential mitigate this in older releases).<br clear="none"><br clear="none"></li></ul><h3 id="Camel2.15.0Release-New">New <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a></h3><h3 id="Camel2.15.0Release-New.1">New <a shape="rect" href="components.html">Components</a></h3><ul><li><a shape="rect" href="beanstalk.html">camel-beanstalk</a> - for working with Amazon Beanstalk jobs.</li><li>came-cassandraql -&#160;Cassandra CQL3 support</li><li><code>camel-chunk</code> - for templating with Chunk engine.</li><li><a shape="rect" href="docker.html">camel-docker</a> - to communicate with Docker.</li><li>camel-dozer - Now also as a c
 omponent to convert messages using the Dozer type conversion framework</li><li>camel-github - for integrating with github</li><li>camel-google-calendar -&#160;provides access to&#160;<a shape="rect" class="external-link" href="http://google.com/calendar" rel="nofollow">Google Calendar</a>&#160;via the&#160;<a shape="rect" class="external-link" href="https://developers.google.com/google-apps/calendar/v3/reference/" rel="nofollow">Google Calendar Web APIs</a>.</li><li>camel-google-mail -&#160;provides access to&#160;<a shape="rect" class="external-link" href="http://gmail.com/" rel="nofollow">Gmail</a>&#160;via the&#160;<a shape="rect" class="external-link" href="https://developers.google.com/gmail/api/v1/reference/" rel="nofollow">Google Mail Web APIs</a>.</li><li><a shape="rect" href="hipchat.html">camel-hipchat</a> - to integrate with the Hipchat service</li><li>camel-pgevent -&#160;Component for sending/receiving notifications in PostgreSQL via the pgjdbc-ng driver</li><li>camel-j
 ira - for integrating with JIRA issue tracker</li><li><a shape="rect" href="kura.html">camel-kura</a> - for deploying Camel OSGi routes into <a shape="rect" class="external-link" href="https://eclipse.org/kura/" rel="nofollow">Eclipse Kura</a> M2M container.</li><li>camel-scr - for using Camel with <a shape="rect" class="external-link" href="http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html">SCR</a>&#160;(OSGi declarative services) on OSGi containers such as Apache Karaf</li><li><a shape="rect" href="spring-boot.html">camel-spring-boot</a> - for using Camel with Spring Boot</li><li>camel-test-spring40 - for testing with Spring 4.0.x. camel-test-spring is for Spring 4.1.x onwards.</li><li><a shape="rect" href="scheduler.html">scheduler</a> - for timer based scheduler using a scheduled thread pool and with more functionality.</li></ul><h3 id="Camel2.15.0Release-NewDSL">New DSL</h3><ul><li>Added <strong>removeProperties</strong> to rem
 ove the properties from exchange.</li></ul><h3 id="Camel2.15.0Release-NewAnnotations">New Annotations</h3><h3 id="Camel2.15.0Release-NewDataFormats">New <a shape="rect" href="data-format.html">Data Formats</a></h3><ul><li>camel-univocity-parsers</li></ul><h3 id="Camel2.15.0Release-New.2">New <a shape="rect" href="languages.html">Languages</a></h3><h3 id="Camel2.15.0Release-New.3">New <a shape="rect" href="examples.html">Examples</a></h3><h3 id="Camel2.15.0Release-New.4">New <a shape="rect" href="tutorials.html">Tutorials</a></h3><h2 id="Camel2.15.0Release-KnownIssues">Known Issues</h2><h2 id="Camel2.15.0Release-DependencyUpgrades"><span>Dependency Upgrades</span></h2><ul><li>AWS-Java-SDK 1.8.3 to 1.8.9.1</li><li>Codahale Metrics 3.0 to 3.1</li><li>CXF 3.0.2 to 3.0.3</li><li>Hazelcast 3.3.2 to 3.4</li><li>JAXB 2.2.7 to 2.2.11</li><li>JRuby 1.7.16 to 1.7.18</li><li>Guava 17.0 to 18.0</li><li>Jsch 0.1.50 to 0.1.51</li><li>JsonPath 1.1.0 to 1.2.0</li><li>Spring 4.0.7.RELEASE to 4.1.4.RE
 LEASE</li><li>Spring Security 3.1.7.RELEASE to 3.2.5.RELEASE</li><li>RX Java 0.20 to 1.0.5</li><li>... and many other upgrades</li></ul><h2 id="Camel2.15.0Release-Importantchangestoconsiderwhenupgrading">Important changes to consider when upgrading</h2><ul><li>Spring 4.1.x is now the default out of the box Spring version.</li><li><span style="color: rgb(0,0,0);">Unit testing with Spring 4.0.x requires using camel-test-spring40, as camel-test-spring is for Spring 4.1 or better.</span></li><li><span style="color: rgb(0,0,0);">Remember to add&#160;<code class="java color1">@BootstrapWith</code><code class="java plain">(CamelTestContextBootstrapper.</code><code class="java keyword">class</code><code class="java plain">)</code>&#160;if upgrading from Spring 3.x or 4.0.x to Spring 4.1 onwards, and using the camel-test-spring module.</span></li><li><a shape="rect" href="xslt.html">XSLT</a>&#160;component now require configuring&#160;<code>transformerFactory</code> using&#160;<a shape="rect
 " href="uris.html">URIs</a> with the #syntax to refer to a bean. Just like any other component would do.</li><li>Slight refactor in&#160;<code>camel-metrics</code> component which may affect users who are using the java endpoint types instead of configuring using uris</li><li><code>camel-csv</code> upgraded to Commons CSV 1.x which has a different API than the old 0.x version. End users may need to adjust their code.</li><li><code>camel-sjms</code> has been refactored a bit to further harden this component.&#160;End users may need to adjust their code.</li><li>The <a shape="rect" href="simple.html">simple</a> function properties:locations:key has been renamed to properties-location:locations:key, as it would clash with the new functionality to specify a default value after the key name, eg properties:key:default</li><li>Removed the backlog tracer commands from the Karaf Camel commands as they are not suitable for a CLI environment</li><li>The need for runtime specific servlets in <a
  shape="rect" href="swagger.html">Swagger</a>&#160;has been removed, and instead just use the default servlet which is provided out of the box.&#160;</li><li><code>org.apache.camel.spi.InflightRepository</code> now includes additional methods for browsing in-flight exchanges.</li><li>Using ?exchangePattern=InOnly or InOut in endpoint uris now take precedence as the pattern in use when sending to the endpoint, using to/recipient list.</li><li><code>DefaultClassLoader</code> now fallback and use the application context classloader that may have been set on&#160;<code>CamelContext</code> to better be able to load classes/resources from classpath in different runtime environments.</li><li><a shape="rect" href="mail.html">Mail</a>&#160;component no longer includes headers starting with&#160;<code>Camel</code> in their keys, as those are consider internal headers and should not be included in the sent emails.</li><li>Removing a route now also remove its static&#160;<a shape="rect" href="e
 ndpoint.html">Endpoint</a>'s from the&#160;<code>EndpointRegistry</code> (if those endpoints are not shared and used by other routes). Mind that any dynamic endpoint created during routing from dynamic&#160;<a shape="rect" href="eip.html">EIP</a>s such as recipient list, routing slip, dynamic router etc, are not removed from the <code>EndpointRegistry</code>&#160;when the route is removed.</li><li>All boolean isFoo methods on the model classes has been removed to ensure the model has consistent java bean getter/setter style with exactly one getter and one setter of the same type.</li><li>The exchange property language has been renamed from property to exchangeProperty&#160;<span>to avoid ambiguity, confusion and clash with properties as a general term. So use exchangeProperty instead of property.</span></li><li>camel-box now uses the CamelBox.folderId as a header instead of exchange property to use control the folder id when uploading to box</li><li>The delay option in <a shape="rec
 t" href="snmp.html">SNMP</a> has changed from using seconds to millis as time unit.</li><li>Routing starting from a&#160;<a shape="rect" href="bean.html">Bean</a>&#160;endpoint is not supported (which wasnt really intended anyway), instead start with a scheduler and use to bean instead.</li><li>Added&#160;<code>copy</code> method to&#160;<code>StreamCache</code> api for&#160;<a shape="rect" href="stream-caching.html">Stream caching</a><br clear="none"><br clear="none"></li></ul><h2 id="Camel2.15.0Release-GettingtheDistributions">Getting the Distributions</h2><h3 id="Camel2.15.0Release-BinaryDistributions">Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd
 "><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.15.0/apache-camel-x.y.x.zip">apache-camel-2.15.0.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/camel/apache-camel/2.15.0/apache-camel-x.y.x.zip.asc">apache-camel-2.15.0.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.15.0/apache-camel-x.y.x.tar.gz">apache-camel-2.15.0.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/camel/apache-camel/2.15.0/apache-camel-x.y.x.tar.gz.asc">apache-camel-2.15.0.ta
 r.gz.asc</a></p></td></tr></tbody></table></div>    <div class="aui-message hint shadowed information-macro">
                     <p class="title">The above URLs use redirection</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">

Modified: websites/production/camel/content/component-list.html
==============================================================================
--- websites/production/camel/content/component-list.html (original)
+++ websites/production/camel/content/component-list.html Sat Feb 21 15:18:33 2015
@@ -480,7 +480,10 @@ disruptor-vm:someName[?&lt;option&gt;]
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To integrate with Salesforce</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="sap-netweaver.html">SAP NetWeaver</a> / camel-sap-netweaver</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[sap-netweaver:hostName[:port][?options]
 ]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To integrate with <a shape="rect" class="external-link" href="http://scn.sap.com/docs/DOC-31221" rel="nofollow">SAP NetWeaver Gateway</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="schematron.html">schematron</a> / camel-schematron</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To integrate with <a shape="rect" class="external-link" href="http://scn.sap.com/docs/DOC-31221" rel="nofollow">SAP NetWeaver Gateway</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="scheduler.html">Scheduler</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[scheduler://name?[options]
+]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to generate message exchanges when a scheduler fires. The scheduler has more functionality than the <a shape="rect" href="timer.html">timer</a> component.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="schematron.html">schematron</a> / camel-schematron</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[schematron://path?[options]
 ]]></script>
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd">Camel component of <a shape="rect" class="external-link" href="http://www.schematron.com/index.html" rel="nofollow">Schematron</a>&#160;which supports to validate the XML instance documents.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="seda.html">SEDA</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">

Modified: websites/production/camel/content/components.html
==============================================================================
--- websites/production/camel/content/components.html (original)
+++ websites/production/camel/content/components.html Sat Feb 21 15:18:33 2015
@@ -489,7 +489,10 @@ disruptor-vm:someName[?&lt;option&gt;]
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To integrate with Salesforce</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="sap-netweaver.html">SAP NetWeaver</a> / camel-sap-netweaver</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[sap-netweaver:hostName[:port][?options]
 ]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To integrate with <a shape="rect" class="external-link" href="http://scn.sap.com/docs/DOC-31221" rel="nofollow">SAP NetWeaver Gateway</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="schematron.html">schematron</a> / camel-schematron</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To integrate with <a shape="rect" class="external-link" href="http://scn.sap.com/docs/DOC-31221" rel="nofollow">SAP NetWeaver Gateway</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="scheduler.html">Scheduler</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[scheduler://name?[options]
+]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to generate message exchanges when a scheduler fires. The scheduler has more functionality than the <a shape="rect" href="timer.html">timer</a> component.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="schematron.html">schematron</a> / camel-schematron</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[schematron://path?[options]
 ]]></script>
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd">Camel component of <a shape="rect" class="external-link" href="http://www.schematron.com/index.html" rel="nofollow">Schematron</a>&#160;which supports to validate the XML instance documents.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="seda.html">SEDA</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">

Modified: websites/production/camel/content/hazelcast-idempotent-repository-tutorial.html
==============================================================================
--- websites/production/camel/content/hazelcast-idempotent-repository-tutorial.html (original)
+++ websites/production/camel/content/hazelcast-idempotent-repository-tutorial.html Sat Feb 21 15:18:33 2015
@@ -85,55 +85,17 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="HazelcastIdempotentRepositoryTutorial-HazelcastIdempotentRepositoryTutorial">Hazelcast Idempotent Repository Tutorial</h2>
-
-<h3 id="HazelcastIdempotentRepositoryTutorial-Overview">Overview</h3>
-
-<p>Apache Camel enables you to integrate the Idempotent Consumer Pattern in a really simple way. In this tutorial we will setup a cluster consisting of two OSGi containers (Apache Karaf). Inside this both nodes we will deploy two equal Camel bundles. This two bundles will receive a message from a REST interface, send them via a Hazelcast SEDA queue and finally store it into a distributed Hazelcast map. To avoid that a (equal) message will be consumed twice we're using the idempotent repository implementation based on Hazelcast. This implementation guarantees cluster wide that no message will be processed twice. </p>
-
-<h3 id="HazelcastIdempotentRepositoryTutorial-WhentoUse">When to Use</h3>
-
-<p>If you use camel in a clustered environment (2 nodes or more) and you have to be sure that two equal messages never will be processed twice. </p>
-
-<h4 id="HazelcastIdempotentRepositoryTutorial-Whytouse">Why to use</h4>
-
-<p>Because you can create with very few effort a Idempotent Repository over n nodes inside your Camel application.</p>
-
-<h3 id="HazelcastIdempotentRepositoryTutorial-HowtoUse">How to Use</h3>
-
-<p>We will create a camel route with a restlet consumer and a hazelcast producer. These routes will be deployed on the servers and form our cluster.</p>
-
-<p><span style="text-decoration: underline;">Preconsideration</span></p>
-
-<p>The restlet consumer will get XML strings that represent an invoice:</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;Invoice id=&quot;${number}&quot;&gt;
+<div class="wiki-content maincontent"><h2 id="HazelcastIdempotentRepositoryTutorial-HazelcastIdempotentRepositoryTutorial">Hazelcast Idempotent Repository Tutorial</h2><h3 id="HazelcastIdempotentRepositoryTutorial-Overview">Overview</h3><p>Apache Camel enables you to integrate the Idempotent Consumer Pattern in a really simple way. In this tutorial we will setup a cluster consisting of two OSGi containers (Apache Karaf). Inside this both nodes we will deploy two equal Camel bundles. This two bundles will receive a message from a REST interface, send them via a Hazelcast SEDA queue and finally store it into a distributed Hazelcast map. To avoid that a (equal) message will be consumed twice we're using the idempotent repository implementation based on Hazelcast. This implementation guarantees cluster wide that no message will be processed twice.</p><h3 id="HazelcastIdempotentRepositoryTutorial-WhentoUse">When to Use</h3><p>If you use camel in a clustered environment (2 nodes or more) 
 and you have to be sure that two equal messages never will be processed twice.</p><h4 id="HazelcastIdempotentRepositoryTutorial-Whytouse">Why to use</h4><p>Because you can create with very few effort a Idempotent Repository over n nodes inside your Camel application.</p><h3 id="HazelcastIdempotentRepositoryTutorial-HowtoUse">How to Use</h3><p>We will create a camel route with a restlet consumer and a hazelcast producer. These routes will be deployed on the servers and form our cluster.</p><p><span style="text-decoration: underline;">Preconsideration</span></p><p>The restlet consumer will get XML strings that represent an invoice:</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;Invoice id=&quot;${number}&quot;&gt;
 	&lt;Article name=&quot;foo&quot;/&gt;
 &lt;/Invoice&gt; 
 ]]></script>
-</div></div>
-
-<p>The Invoice id will be our Unique message ID.<br clear="none">
-We will then send multiple invoice messages to the restlet consumer. Hazelcast will spread these files throughout the cluster and write them to files. Because of the Idempotent Consumer Pattern no duplicate files should occur on our cluster.</p>
-
-
-<p><span style="text-decoration: underline;">Setup</span></p>
-
-<p>You will need two servers with an OSGI runtime environment (we will use Karaf in this tutorial). </p>
-
-<p>In the Karaf console add the camel features and install the needed packages:</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[
-features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.8-SNAPSHOT/xml/features
+</div></div><p>The Invoice id will be our Unique message ID.<br clear="none"> We will then send multiple invoice messages to the restlet consumer. Hazelcast will spread these files throughout the cluster and write them to files. Because of the Idempotent Consumer Pattern no duplicate files should occur on our cluster.</p><p><span style="text-decoration: underline;">Setup</span></p><p>You will need two servers with an OSGI runtime environment (we will use Karaf in this tutorial).</p><p>In the Karaf console add the camel features and install the needed packages:</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[features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.8-SNAPSHOT/xml/features
 features:install camel-core camel-spring camel-hazelcast
 ]]></script>
-</div></div>
-
-<p>Our routes (similar on both nodes):</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[
-package org.apache.camel.tutorial.routes;
+</div></div><p>Our routes (similar on both nodes):</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[package org.apache.camel.tutorial.routes;
 
 import org.apache.camel.builder.RouteBuilder;
 import org.apache.camel.component.hazelcast.HazelcastConstants;
@@ -162,12 +124,8 @@ public class RoutesHazelcast extends Rou
 	}
 }
 ]]></script>
-</div></div>
-
-<p>Testing the routes <img class="emoticon emoticon-wink" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/wink.png" data-emoticon-name="wink" alt="(wink)">:</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[
-package org.apache.camel.tutorial.idempotent;
+</div></div><p>Testing the routes <img class="emoticon emoticon-wink" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/wink.png" data-emoticon-name="wink" alt="(wink)">:</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[package org.apache.camel.tutorial.idempotent;
 
 import org.apache.camel.test.junit4.CamelSpringTestSupport;
 import org.junit.Test;
@@ -218,12 +176,8 @@ public class HazelcastIdempotenRepositor
 
 }
 ]]></script>
-</div></div>
-
-<p>Our camel-context.xml</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;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+</div></div><p>Our camel-context.xml</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;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 
 &lt;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot;
 	xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
@@ -237,12 +191,8 @@ public class HazelcastIdempotenRepositor
 	&lt;/camelContext&gt;
 &lt;/beans&gt;
 ]]></script>
-</div></div>
-
-<p>The pom.xml:</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;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+</div></div><p>The pom.xml:</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;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 
 &lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
 	xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd&quot;&gt;
@@ -343,30 +293,14 @@ public class HazelcastIdempotenRepositor
 
 &lt;/project&gt;
 ]]></script>
-</div></div>
-
-<p>Switch to your project directory and build the jar (with maven):</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[
-mvn clean install
+</div></div><p>Switch to your project directory and build the jar (with maven):</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[mvn clean install
 ]]></script>
-</div></div>
-
-
-<p>Copy the jar to your servers and install them in Karaf:</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[
-osgi:install file:/home/username/HazelcastIdempotenRepository-1.0.0.jar
+</div></div><p>Copy the jar to your servers and install them in Karaf:</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[osgi:install file:/home/username/HazelcastIdempotenRepository-1.0.0.jar
 ]]></script>
-</div></div>
-
-
-<p><span style="text-decoration: underline;">Validate</span></p>
-
-<p>In the java project create a class with the following code:</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[
-package org.apache.camel.tutorial;
+</div></div><p><span style="text-decoration: underline;">Validate</span></p><p>In the java project create a class with the following code:</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[package org.apache.camel.tutorial;
 
 import java.util.Random;
 
@@ -455,21 +389,13 @@ public class HazelcastIdempotenRepositor
 	}
 }
 ]]></script>
-</div></div>
-
-<p>While executing the project the console will output the send and received messages:</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[
-[           		    foo] route1                         INFO  sending message to &#39;host1&#39;  --&gt;  &lt;Invoice id=&quot;20&quot;&gt;&lt;Article name=&quot;foo&quot;/&gt;&lt;/Invoice&gt;
-[Instance_0_dev.cached.thread-3] route2                         INFO  --- new message received ---
-[                           foo] route1                         INFO  sending message to &#39;host1&#39;  --&gt;  &lt;Invoice id=&quot;1&quot;&gt;&lt;Article name=&quot;foo&quot;/&gt;&lt;/Invoice&gt;
-[                           foo] route1                         INFO  sending message to &#39;host2&#39;  --&gt;  &lt;Invoice id=&quot;16&quot;&gt;&lt;Article name=&quot;foo&quot;/&gt;&lt;/Invoice&gt;
+</div></div><p>While executing the project the console will output the send and received messages:</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[[        foo] route1 INFO  sending message to &#39;host1&#39;  --&gt;  &lt;Invoice id=&quot;20&quot;&gt;&lt;Article name=&quot;foo&quot;/&gt;&lt;/Invoice&gt;
+[...thread-3] route2 INFO  --- new message received ---
+[        foo] route1 INFO  sending message to &#39;host1&#39;  --&gt;  &lt;Invoice id=&quot;1&quot;&gt;&lt;Article name=&quot;foo&quot;/&gt;&lt;/Invoice&gt;
+[        foo] route1 INFO  sending message to &#39;host2&#39;  --&gt;  &lt;Invoice id=&quot;16&quot;&gt;&lt;Article name=&quot;foo&quot;/&gt;&lt;/Invoice&gt;
 ]]></script>
-</div></div>
-
-<p>If the message hasn't been sent before, you will get a <code>"new message received"</code>, if the message is already in the idempotent repository it won't be processed. If you let run the script for a minute there should be almost no <code>"new message received"</code> log out printed.  </p>
-
-</div>
+</div></div><p>If the message hasn't been sent before, you will get a <code>"new message received"</code>, if the message is already in the idempotent repository it won't be processed. If you let run the script for a minute there should be almost no <code>"new message received"</code> log out printed.</p></div>
         </td>
         <td valign="top">
           <div class="navigation">

Modified: websites/production/camel/content/polling-consumer.html
==============================================================================
--- websites/production/camel/content/polling-consumer.html (original)
+++ websites/production/camel/content/polling-consumer.html Sat Feb 21 15:18:33 2015
@@ -202,7 +202,7 @@ public static class MyCoolBean {
     }
 }
 ]]></script>
-</div></div><h3 id="PollingConsumer-ScheduledPollComponents">Scheduled Poll Components</h3><p>Quite a few inbound Camel endpoints use a scheduled poll pattern to receive messages and push them through the Camel processing routes. That is to say externally from the client the endpoint appears to use an <a shape="rect" href="event-driven-consumer.html">Event Driven Consumer</a> but internally a scheduled poll is used to monitor some kind of state or resource and then fire message exchanges.</p><p>Since this a such a common pattern, polling components can extend the <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/ScheduledPollConsumer.html">ScheduledPollConsumer</a> base class which makes it simpler to implement this pattern.</p><p>There is also the <a shape="rect" href="quartz.html">Quartz Component</a> which provides scheduled delivery of messages using the Quartz enterprise scheduler.</p><p>For more details s
 ee:</p><ul><li><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/PollingConsumer.html">PollingConsumer</a></li><li>Scheduled Polling Components<ul><li><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/ScheduledPollConsumer.html">ScheduledPollConsumer</a></li><li><a shape="rect" href="atom.html">Atom</a></li><li><a shape="rect" href="beanstalk.html">Beanstalk</a></li><li><a shape="rect" href="file2.html">File</a></li><li><a shape="rect" href="ftp2.html">FTP</a></li><li><a shape="rect" href="hbase.html">hbase</a></li><li><a shape="rect" href="ibatis.html">iBATIS</a></li><li><a shape="rect" href="jpa.html">JPA</a></li><li><a shape="rect" href="mail.html">Mail</a></li><li><a shape="rect" href="mybatis.html">MyBatis</a></li><li><a shape="rect" href="quartz.html">Quartz</a></li><li><a shape="rect" href="snmp.html">SNMP</a></li><li><a shape="rect" hre
 f="aws-s3.html">AWS-S3</a></li><li><a shape="rect" href="aws-sqs.html">AWS-SQS</a></li></ul></li></ul><h3 id="PollingConsumer-ScheduledPollConsumerOptions">ScheduledPollConsumer Options</h3><p>The ScheduledPollConsumer supports the following options:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>pollStrategy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"><p>A pluggable <code>org.apache.camel.PollingConsumerPollingStrategy</code> allowing you to provide your custom implementation to control error handling usually occurred during the <code>poll</code> operation <strong>before</strong>
  an <a shape="rect" href="exchange.html">Exchange</a> have been created and being routed in Camel. In other words the error occurred while the polling was gathering information, for instance access to a file network failed so Camel cannot access it to scan for files. The default implementation will log the caused exception at <code>WARN</code> level and ignore it.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>sendEmptyMessageWhenIdle</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.9:</strong> If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>startScheduler</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Wh
 ether the scheduler should be auto started.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>initialDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Milliseconds before the first poll starts.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>delay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Milliseconds before the next poll.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useFixedDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Controls if fixed delay or fixed rate is used. See <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ScheduledExecutorService.html" rel="no
 follow">ScheduledExecutorService</a> in JDK for details. In <strong>Camel 2.7.x</strong> or older the default value is <code>false</code>. From <strong>Camel 2.8</strong> onwards the default value is <code>true</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>timeUnit</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>TimeUnit.MILLISECONDS</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>time unit for <code>initialDelay</code> and <code>delay</code> options.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>runLoggingLevel</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>TRACE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.8:</strong> The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><co
 de>scheduledExecutorService</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.10:</strong> Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. This option allows you to share a thread pool among multiple consumers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>greedy</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.10.6/2.11.1:</strong> If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>scheduler</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colsp
 an="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong> Allow to plugin a custom <code>org.apache.camel.spi.ScheduledPollConsumerScheduler</code> to use as the scheduler for firing when the polling consumer runs. The default implementation uses the <code>ScheduledExecutorService</code> and there is a <a shape="rect" href="quartz2.html">Quartz2</a>, and <a shape="rect" href="spring.html">Spring</a> based which supports CRON expressions. <strong>Notice:</strong> If using a custom scheduler then the options for <code>initialDelay</code>, <code>useFixedDelay</code>, <code>timeUnit</code>, and <code>scheduledExecutorService</code> may not be in use. Use the text <code>quartz2</code> to refer to use the <a shape="rect" href="quartz2.html">Quartz2</a> scheduler; and use the text <code>spring</code> to use the <a shape="rect" href="spring.html">Spring</a> based; and use the text <code>#myScheduler</code> to refer to a custom scheduler by its id in the <a shape="rect" href="r
 egistry.html">Registry</a>. See <a shape="rect" href="quartz2.html">Quartz2</a> page for an example.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>scheduler.xxx</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.12:</strong> To configure additional properties when using a custom <code>scheduler</code> or any of the <a shape="rect" href="quartz2.html">Quartz2</a>, <a shape="rect" href="spring.html">Spring</a> based scheduler.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>backoffMultiplier</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong> To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be
  skipped before the next actual attempt is happening again. When this option is in use then <code>backoffIdleThreshold</code> and/or <code>backoffErrorThreshold</code> must also be configured.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>backoffIdleThreshold</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong> The number of subsequent idle polls that should happen before the <code>backoffMultipler</code> should kick-in.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>backoffErrorThreshold</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong> The number of subsequent error polls (failed due some error) that should happen before the <code>backoffMultipler</code> should kick-in.</p></td></tr></tbody
 ></table></div></div><h3 id="PollingConsumer-Usingbackofftolettheschedulerbelessaggressive">Using backoff to let the scheduler be less aggressive</h3><p><strong>Available as of Camel 2.12</strong></p><p>The scheduled <a shape="rect" href="polling-consumer.html">Polling Consumer</a> is by default static by using the same poll frequency whether or not there is messages to pickup or not. From Camel 2.12 onwards you can configure the scheduled <a shape="rect" href="polling-consumer.html">Polling Consumer</a> to be more dynamic by using backoff. This allows the scheduler to skip N number of polls when it becomes idle, or there has been X number of errors in a row. See more details in the table above for the <code>backoffXXX</code> options.</p><p>For example to let a FTP consumer backoff if its becoming idle for a while you can do:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="PollingConsumer-ScheduledPollComponents">Scheduled Poll Components</h3><p>Quite a few inbound Camel endpoints use a scheduled poll pattern to receive messages and push them through the Camel processing routes. That is to say externally from the client the endpoint appears to use an <a shape="rect" href="event-driven-consumer.html">Event Driven Consumer</a> but internally a scheduled poll is used to monitor some kind of state or resource and then fire message exchanges.</p><p>Since this a such a common pattern, polling components can extend the <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/ScheduledPollConsumer.html">ScheduledPollConsumer</a> base class which makes it simpler to implement this pattern.</p><p>There is also the <a shape="rect" href="quartz.html">Quartz Component</a> which provides scheduled delivery of messages using the Quartz enterprise scheduler.</p><p>For more details s
 ee:</p><ul><li><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/PollingConsumer.html">PollingConsumer</a></li><li>Scheduled Polling Components<ul><li><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/ScheduledPollConsumer.html">ScheduledPollConsumer</a></li><li><a shape="rect" href="scheduler.html">Scheduler</a></li><li><a shape="rect" href="atom.html">Atom</a></li><li><a shape="rect" href="beanstalk.html">Beanstalk</a></li><li><a shape="rect" href="file2.html">File</a></li><li><a shape="rect" href="ftp2.html">FTP</a></li><li><a shape="rect" href="hbase.html">hbase</a></li><li><a shape="rect" href="ibatis.html">iBATIS</a></li><li><a shape="rect" href="jpa.html">JPA</a></li><li><a shape="rect" href="mail.html">Mail</a></li><li><a shape="rect" href="mybatis.html">MyBatis</a></li><li><a shape="rect" href="quartz.html">Quartz</a></li><li><a shape=
 "rect" href="snmp.html">SNMP</a></li><li><a shape="rect" href="aws-s3.html">AWS-S3</a></li><li><a shape="rect" href="aws-sqs.html">AWS-SQS</a></li></ul></li></ul><h3 id="PollingConsumer-ScheduledPollConsumerOptions">ScheduledPollConsumer Options</h3><p>The ScheduledPollConsumer supports the following options:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>pollStrategy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"><p>A pluggable <code>org.apache.camel.PollingConsumerPollingStrategy</code> allowing you to provide your custom implementation to control error handling usually occurred du
 ring the <code>poll</code> operation <strong>before</strong> an <a shape="rect" href="exchange.html">Exchange</a> have been created and being routed in Camel. In other words the error occurred while the polling was gathering information, for instance access to a file network failed so Camel cannot access it to scan for files. The default implementation will log the caused exception at <code>WARN</code> level and ignore it.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>sendEmptyMessageWhenIdle</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.9:</strong> If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>startScheduler</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p
 ></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether the scheduler should be auto started.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>initialDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Milliseconds before the first poll starts.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>delay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Milliseconds before the next poll.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useFixedDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Controls if fixed delay or fixed rate is used. See <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api
 /java/util/concurrent/ScheduledExecutorService.html" rel="nofollow">ScheduledExecutorService</a> in JDK for details. In <strong>Camel 2.7.x</strong> or older the default value is <code>false</code>. From <strong>Camel 2.8</strong> onwards the default value is <code>true</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>timeUnit</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>TimeUnit.MILLISECONDS</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>time unit for <code>initialDelay</code> and <code>delay</code> options.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>runLoggingLevel</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>TRACE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.8:</strong> The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.</p></td></tr
 ><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>scheduledExecutorService</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.10:</strong> Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. This option allows you to share a thread pool among multiple consumers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>greedy</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.10.6/2.11.1:</strong> If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>scheduler</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.12:</strong> Allow to plugin a custom <code>org.apache.camel.spi.ScheduledPollConsumerScheduler</code> to use as the scheduler for firing when the polling consumer runs. The default implementation uses the <code>ScheduledExecutorService</code> and there is a <a shape="rect" href="quartz2.html">Quartz2</a>, and <a shape="rect" href="spring.html">Spring</a> based which supports CRON expressions. <strong>Notice:</strong> If using a custom scheduler then the options for <code>initialDelay</code>, <code>useFixedDelay</code>, <code>timeUnit</code>, and <code>scheduledExecutorService</code> may not be in use. Use the text <code>quartz2</code> to refer to use the <a shape="rect" href="quartz2.html">Quartz2</a> scheduler; and use the text <code>spring</code> to use the <a shape="rect" href="spring.html">Spring</a> based; and use the text <code>#myScheduler</code> to refer to
  a custom scheduler by its id in the <a shape="rect" href="registry.html">Registry</a>. See <a shape="rect" href="quartz2.html">Quartz2</a> page for an example.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>scheduler.xxx</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.12:</strong> To configure additional properties when using a custom <code>scheduler</code> or any of the <a shape="rect" href="quartz2.html">Quartz2</a>, <a shape="rect" href="spring.html">Spring</a> based scheduler.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>backoffMultiplier</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong> To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a 
 row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then <code>backoffIdleThreshold</code> and/or <code>backoffErrorThreshold</code> must also be configured.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>backoffIdleThreshold</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong> The number of subsequent idle polls that should happen before the <code>backoffMultipler</code> should kick-in.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>backoffErrorThreshold</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong> The number of subsequent error polls (failed due some error) that should happen before the <code>
 backoffMultipler</code> should kick-in.</p></td></tr></tbody></table></div></div><h3 id="PollingConsumer-Usingbackofftolettheschedulerbelessaggressive">Using backoff to let the scheduler be less aggressive</h3><p><strong>Available as of Camel 2.12</strong></p><p>The scheduled <a shape="rect" href="polling-consumer.html">Polling Consumer</a> is by default static by using the same poll frequency whether or not there is messages to pickup or not. From Camel 2.12 onwards you can configure the scheduled <a shape="rect" href="polling-consumer.html">Polling Consumer</a> to be more dynamic by using backoff. This allows the scheduler to skip N number of polls when it becomes idle, or there has been X number of errors in a row. See more details in the table above for the <code>backoffXXX</code> options.</p><p>For example to let a FTP consumer backoff if its becoming idle for a while you can do:</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;ftp://myserver?username=foo&amp;passowrd=secret?delete=true&amp;delay=5s&amp;backoffMultiplier=6&amp;backoffIdleThreshold=5&quot;)
       .to(&quot;bean:processFile&quot;);
 ]]></script>



Mime
View raw message