You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2016/05/24 11:19:44 UTC
svn commit: r989029 [1/2] - in /websites/production/camel/content:
book-architecture.html book-in-one-page.html cache/main.pageCache
camel-2180-release.html component-list.html component.html components.html
consul-component.html transport.html uris.html
Author: buildbot
Date: Tue May 24 11:19:43 2016
New Revision: 989029
Log:
Production update by buildbot for camel
Added:
websites/production/camel/content/consul-component.html
Modified:
websites/production/camel/content/book-architecture.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-2180-release.html
websites/production/camel/content/component-list.html
websites/production/camel/content/component.html
websites/production/camel/content/components.html
websites/production/camel/content/transport.html
websites/production/camel/content/uris.html
Modified: websites/production/camel/content/book-architecture.html
==============================================================================
--- websites/production/camel/content/book-architecture.html (original)
+++ websites/production/camel/content/book-architecture.html Tue May 24 11:19:43 2016
@@ -192,7 +192,9 @@ Camel uses a Java based <a shape="rect"
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses the <a shape="rect" class="external-link" href="http://chemistry.apache.org/java/opencmis.html">Apache Chemistry</a> client API to interface with CMIS supporting CMS</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cometd.html">Cometd</a> / camel-cometd</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cometd://hostName:port/channelName[?options]
]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="context.html">Context</a> / camel-context</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>Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="consul-component.html">Consul</a> / camel-consul</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[consul:apiEndpoint[?options]]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><span>For interfacing with an </span><span> </span><a shape="rect" class="external-link" href="https://www.consul.io/" rel="nofollow">Consul</a>.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="context.html">Context</a> / camel-context</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[context:camelContextId:localEndpointName[?options]
]]></script>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to refer to endpoints within a separate CamelContext to provide a simple <a shape="rect" href="context.html">black box composition</a> approach so that routes can be combined into a CamelContext and then used as a black box component inside other routes in other CamelContexts</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="controlbus-component.html">ControlBus</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Tue May 24 11:19:43 2016
@@ -536,7 +536,9 @@ Camel uses a Java based <a shape="rect"
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses the <a shape="rect" class="external-link" href="http://chemistry.apache.org/java/opencmis.html">Apache Chemistry</a> client API to interface with CMIS supporting CMS</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cometd.html">Cometd</a> / camel-cometd</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cometd://hostName:port/channelName[?options]
]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="context.html">Context</a> / camel-context</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>Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="consul-component.html">Consul</a> / camel-consul</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[consul:apiEndpoint[?options]]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><span>For interfacing with an </span><span> </span><a shape="rect" class="external-link" href="https://www.consul.io/" rel="nofollow">Consul</a>.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="context.html">Context</a> / camel-context</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[context:camelContextId:localEndpointName[?options]
]]></script>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to refer to endpoints within a separate CamelContext to provide a simple <a shape="rect" href="context.html">black box composition</a> approach so that routes can be combined into a CamelContext and then used as a black box component inside other routes in other CamelContexts</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="controlbus-component.html">ControlBus</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -3617,11 +3619,11 @@ The tutorial has been designed in two pa
While not actual tutorials you might find working through the source of the various <a shape="rect" href="examples.html">Examples</a> useful.</li></ul>
<h2 id="BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</h2><p> </p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Thanks</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This tutorial was kindly donated to Apache Camel by Martin Gilday.</p></div></div><h2 id="BookInOnePage-Preface">Preface</h2><p>This tutorial aims to guide the reader through the stages of creating a project which uses Camel to facilitate the routing of messages from a JMS queue to a <a shape="rect" class="external-link" href="http://www.springramework.org" rel="nofollow">Spring</a> service. The route works in a synchronous fashion returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1464085083028 {padding: 0px;}
-div.rbtoc1464085083028 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1464085083028 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1464088674578 {padding: 0px;}
+div.rbtoc1464088674578 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1464088674578 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1464085083028">
+/*]]>*/</style></p><div class="toc-macro rbtoc1464088674578">
<ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</a></li><li><a shape="rect" href="#BookInOnePage-Preface">Preface</a></li><li><a shape="rect" href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect" href="#BookInOnePage-About">About</a></li><li><a shape="rect" href="#BookInOnePage-CreatetheCamelProject">Create the Camel Project</a>
<ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-UpdatethePOMwithDependencies">Update the POM with Dependencies</a></li></ul>
</li><li><a shape="rect" href="#BookInOnePage-WritingtheServer">Writing the Server</a>
@@ -5736,11 +5738,11 @@ So we completed the last piece in the pi
<p>This example has been removed from <strong>Camel 2.9</strong> onwards. Apache Axis 1.4 is a very old and unsupported framework. We encourage users to use <a shape="rect" href="cxf.html">CXF</a> instead of Axis.</p></div></div>
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1464085083254 {padding: 0px;}
-div.rbtoc1464085083254 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1464085083254 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1464088674823 {padding: 0px;}
+div.rbtoc1464088674823 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1464088674823 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1464085083254">
+/*]]>*/</style><div class="toc-macro rbtoc1464088674823">
<ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis 1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect" href="#BookInOnePage-Introduction">Introduction</a></li><li><a shape="rect" href="#BookInOnePage-SettinguptheprojecttorunAxis">Setting up the project to run Axis</a>
<ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-Maven2">Maven 2</a></li><li><a shape="rect" href="#BookInOnePage-wsdl">wsdl</a></li><li><a shape="rect" href="#BookInOnePage-ConfiguringAxis">Configuring Axis</a></li><li><a shape="rect" href="#BookInOnePage-RunningtheExample">Running the Example</a></li></ul>
@@ -17137,11 +17139,11 @@ template.send("direct:alias-verify&
]]></script>
</div></div><p></p><h3 id="BookInOnePage-SeeAlso.28">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="crypto.html">Crypto</a> Crypto is also available as a <a shape="rect" href="data-format.html">Data Format</a></li></ul> <h2 id="BookInOnePage-CXFComponent">CXF Component</h2><div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>When using CXF as a consumer, the <a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows you to factor out how message payloads are received from their processing as a RESTful or SOAP web service. This has the potential of using a multitude of transports to consume web
services. The bean component's configuration is also simpler and provides the fastest method to implement web services using Camel and CXF.</p></div></div><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>When using CXF in streaming modes (see DataFormat option), then also read about <a shape="rect" href="stream-caching.html">Stream caching</a>.</p></div></div><p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1464085094141 {padding: 0px;}
-div.rbtoc1464085094141 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1464085094141 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1464088707596 {padding: 0px;}
+div.rbtoc1464088707596 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1464088707596 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1464085094141">
+/*]]>*/</style></p><div class="toc-macro rbtoc1464088707596">
<ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-URIformat">URI format</a></li><li><a shape="rect" href="#BookInOnePage-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>
@@ -25213,7 +25215,7 @@ protected RouteBuilder createRouteBuilde
</dependency>
]]></script>
</div></div><h3 id="BookInOnePage-SMSlimitations">SMS limitations</h3><p>SMS is neither reliable or secure.  Users who require reliable and secure delivery may want to consider using the XMPP or SIP components instead, combined with a smartphone app supporting the chosen protocol.</p><ul><li>Reliability: although the SMPP standard offers a range of feedback mechanisms to indicate errors, non-delivery and confirmation of delivery it is not uncommon for mobile networks to hide or simulate these responses.  For example, some networks automatically send a delivery confirmation for every message even if the destination number is invalid or not switched on.  Some networks silently drop messages if they think they are spam.  Spam detection rules in the network may be very crude, sometimes more than 100 messages per day from a single sender may be considered spam.</li><li>Security: there is basic encryption for the last hop from the radio tower down to the recipient hand
set.  SMS messages are not encrypted or authenticated in any other part of the network.  Some operators allow staff in retail outlets or call centres to browse through the SMS message histories of their customers.  Message sender identity can be easily forged.  Regulators and even the mobile telephone industry itself has cautioned against the use of SMS in two-factor authentication schemes and other purposes where security is important.</li></ul><p>While the Camel component makes it as easy as possible to send messages to the SMS network, it can not offer an easy solution to these problems.</p><h2 id="BookInOnePage-Datacoding,alphabetandinternationalcharactersets">Data coding, alphabet and international character sets</h2><p>Data coding and alphabet can be specified on a per-message basis.  Default values can be specified for the endpoint.  It is important to understand the relationship between these options and the way the component acts when more than
one value is set.</p><p>Data coding is an 8 bit field in the SMPP wire format.</p><p>Alphabet corresponds to bits 0-3 of the data coding field.  For some types of message, where a message class is used (by setting bit 5 of the data coding field), the lower two bits of the data coding field are not interpreted as alphabet and only bits 2 and 3 impact the alphabet.</p><p>Furthermore, current version of the JSMPP library only seems to support bits 2 and 3, assuming that bits 0 and 1 are used for message class.  This is why the Alphabet class in JSMPP doesn't support the value 3 (binary 0011) which indicates ISO-8859-1.</p><p>Although JSMPP provides a representation of the message class parameter, the Camel component doesn't currently provide a way to set it other than manually setting the corresponding bits in the data coding field.</p><p>When setting the data coding field in the outgoing message, the Camel component considers the following values and uses the first one it c
an find:</p><ul><li>the data coding specified in a header</li><li>the alphabet specified in a header</li><li>the data coding specified in the endpoint configuration (URI parameter)</li></ul><p>Older versions of Camel had bugs in support for international character sets.  This feature only worked when a single encoding was used for all messages and was troublesome when users wanted to change it on a per-message basis.  Users who require this to work should ensure their version of Camel includes the fix for </p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: connect timed out
+ <span class="aui-icon icon-warning"></span>JIRA Issues Macro: com.atlassian.sal.api.net.ResponseStatusException: Unexpected response received. Status code: 404
</div>
.<p>In addition to trying to send the data coding value to the SMSC, the Camel component also tries to analyze the message body, convert it to a Java String (Unicode) and convert that to a byte array in the corresponding alphabet  When deciding which alphabet to use in the byte array, the Camel SMPP component does not consider the data coding value (header or configuration), it only considers the specified alphabet (from either the header or endpoint parameter).</p><p>If some characters in the String can't be represented in the chosen alphabet, they may be replaced by the question mark ( ? ) symbol.  Users of the API may want to consider checking if their message body can be converted to ISO-8859-1 before passing it to the component and if not, setting the alphabet header to request UCS-2 encoding.  If the alphabet and data coding options are not specified at all then the component may try to detect the required encoding and set the data coding for you.</p><p>The list
of alphabet codes are specified in the SMPP specification v3.4, section 5.2.19.  One notable limitation of the SMPP specification is that there is no alphabet code for explicitly requesting use of the GSM 3.38 (7 bit) character set.  Choosing the value 0 for the alphabet selects the SMSC <em>default</em> alphabet, this usually means GSM 3.38 but it is not guaranteed.  The SMPP gateway Nexmo <a shape="rect" class="external-link" href="https://help.nexmo.com/hc/en-us/articles/204015813-How-to-change-the-character-encoding-in-SMPP-" rel="nofollow">actually allows the default to be mapped to any other character set with a control panel option</a>. It is suggested that users check with their SMSC operator to confirm exactly which character set is being used as the default.</p><h3 id="BookInOnePage-Messagesplittingandthrottling">Message splitting and throttling</h3><p>After transforming a message body from a String to a byte array, the Camel component is also responsible f
or splitting the message into parts (within the 140 byte SMS size limit) before passing it to JSMPP.  This is completed automatically.</p><p>If the GSM 3.38 alphabet is used, the component will pack up to 160 characters into the 140 byte message body.  If an 8 bit character set is used (e.g. ISO-8859-1 for western Europe) then 140 characters will be allowed within the 140 byte message body.  If 16 bit UCS-2 encoding is used then just 70 characters fit into each 140 byte message.</p><p>Some SMSC providers implement throttling rules.  Each part of a message that has been split may be counted separately by the provider's throttling mechanism.  The Camel Throttler component can be useful for throttling messages in the SMPP route before handing them to the SMSC.</p><h3 id="BookInOnePage-URIformat.62">URI format</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[smpp://[username@]hostname[:port][?options]
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-2180-release.html
==============================================================================
--- websites/production/camel/content/camel-2180-release.html (original)
+++ websites/production/camel/content/camel-2180-release.html Tue May 24 11:19:43 2016
@@ -85,7 +85,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h1 id="Camel2.18.0Release-Camel2.18.0release(currentlyinprogress)">Camel 2.18.0 release (currently in progress)</h1><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><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"></span></p></div><div style="min-height:200px"> </div><h2 id="Camel2.18.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to the 2.18.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p><ul><li>Added <a shape="rect" href="hystrix-eip.html">Hystrix EIP</a> as EIP pattern that uses native Hystrix as the Circuit Breaker implementation. This requires having <code>camel-hsytrix</code> on the classpath.</li><li>Improved the <a
shape="rect" href="bean.html">Bean</a> component to better match method parameter types when using <a shape="rect" href="simple.html">Simple</a> language as parameter values.</li><li>Added <code>BindyConverter</code> that allows to implement custom data converters for <a shape="rect" href="bindy.html">Bindy</a></li><li>The access in the <a shape="rect" href="rest-dsl.html">Rest DSL</a> has been deprecated and no longer in use - its not part of swagger specification anymore.</li><li><a shape="rect" href="nats.html">Camel-NATS</a> now uses JNATS client instead of the deprecated Java_nats one.</li><li>During startup of <a shape="rect" href="camelcontext.html">CamelContext</a> the services that are used as part of routes are now deferred being started to the end of the startup process. Some IoC frameworks like Spring can otherwise causes a circular dependency issue if services are started too early. A side effect is that if service startup failures happen w
hen being started later, they are now wrapped in the <code>FailedToStartupRouteException</code> to better pin point which route thas the problem.</li><li>Improved the startup sequence of <a shape="rect" href="spring-java-config.html">Spring Java Config</a> to be similar to <a shape="rect" href="spring-boot.html">Spring Boot</a> that helps prevent Spring initialization errors about circular dependencies issues.</li><li>Added PATCH to <a shape="rect" href="rest-dsl.html">Rest DSL</a></li><li>Added "starts with" and "ends with" operator to the <a shape="rect" href="simple.html">Simple</a> language.</li><li>Added <code>BeanIOSplitter</code> to <a shape="rect" href="beanio.html">BeanIO</a> that can be used with the <a shape="rect" href="splitter.html">Splitter</a> EIP to split big payloads in streaming mode without reading the entire content into memory.</li><li>Some of the <a shape="rect" href="aws.html">AWS</a> components allows to specify ARN in
the endpoint configuration. </li><li>The create operation in <a shape="rect" href="zookeeper.html">Zookeeper</a> now creates sub paths if missing.</li><li>Added support for async mode for <a shape="rect" href="servlet.html">SERVLET</a> component to leverage Asynchronous Servlet from the Servlet 3.0 spec.</li><li><a shape="rect" href="bean.html">Bean</a> component and <a shape="rect" href="bean-language.html">Bean Language</a> validates method name must be a valid according to java identifier rules, and also if parameter syntax has an ending parenthesis.</li><li>You can now use <code>@RunWith(CamelSpringBootJUnit4ClassRunner.class)</code> to test Camel <a shape="rect" href="spring-boot.html">Spring Boot</a> applications and use the Camel test annotations from <a shape="rect" href="spring-testing.html">Spring Testing</a> such as <code>@MockEndpoints</code>.</li><li>To turn on logging exhausted message body with the message history you
can configure this easily on the CamelContext level with <code>setLogExhaustedMessageBody</code></li><li><a shape="rect" href="infinispan.html">Camel-Infinispan</a> now supports Aggregation Repository: InfinispanLocalAggregationRepository and InfinispanRemoteAggregationRepository</li><li>The <a shape="rect" href="sql-component.html">SQL Component</a> and <a shape="rect" href="elsql.html">ElSql</a> now supports <code>outputType=StreamList</code> to use an iterator for the output of the SQL query that allows to process the data in a streaming fashion such as with the <a shape="rect" href="splitter.html">Splitter</a> EIP to process the data row by row, and load data from the database as needed.</li><li><a shape="rect" href="jpa.html">JPA</a> now includes a <code>JpaPollingConsumer</code> implementation that better supports <a shape="rect" href="content-enricher.html">Content Enricher</a> using <code>pollEnrich</code> to do a on-demand poll
that returns either none, one or a list of entities as the result. </li><li>Calling <a shape="rect" href="bean.html">Bean</a> with method parameters defined using <a shape="rect" href="simple.html">Simple</a> parameters, now avoids an intermediate conversion of the parameters to a String value. This ensures the passed in values when calling the bean method is using the parameter type as-is from <a shape="rect" href="simple.html">Simple</a>.</li><li><a shape="rect" href="cdi.html">Camel CDI</a> now supports importing Camel XML configuration files</li><li><a shape="rect" href="cdi.html">Camel CDI</a> does not deploy an empty Camel context bean anymore if not route builder beans nor Camel beans are deployed</li><li><a shape="rect" href="cdi.html">Camel CDI</a> adds the <code>@Named</code> qualifier to Camel route management events so that it's possible to observe these events for a specific route with an explicit <code>id</code></li><li><a shape=
"rect" href="beanio.html">Camel BeanIO</a> now supports the possibility to use a custom BeanReaderErrorHandler implementation in his configuration</li><li><a shape="rect" href="kubernetes.html">Camel Kubernetes</a> now supports Kubernetes ConfigMap feature</li><li>The <a shape="rect" href="tokenizer.html">Tokenizer</a> and <a shape="rect" href="xmltokenizer.html">XMLTokenizer</a> language now supports using <a shape="rect" href="simple.html">Simple</a> expressions as the token / xml tag names so they can be dynamic values.</li><li>Added <code>filterDirectory</code> and <code>filterFile</code> options to <a shape="rect" href="file2.html">File2</a> so filtering can be done using <a shape="rect" href="simple.html">Simple</a> language or predicates. </li><li>Optimize Camel to only enable AllowUseOriginalMessage if in use by error handler or <a shape="rect" href="oncompletion.html">OnCompletion</a>. End user who manually access the original message
using the Java API must configure AllowUseOriginalMessage=true.</li><li><a shape="rect" href="ahc.html">Camel-AHC</a> now support a connectionClose parameter to allow explicitly adding a Connection Close header to HTTP request</li><li><a shape="rect" href="http.html">Camel-HTTP</a> now support a connectionClose parameter to allow explicitly adding a Connection Close header to HTTP request</li><li><a shape="rect" href="http4.html">Camel-HTTP4</a> now support a connectionClose parameter to allow explicitly adding a Connection Close header to HTTP request</li><li><a shape="rect" href="jetty.html">Camel-Jetty</a> now support a connectionClose parameter to allow explicitly adding a Connection Close header to HTTP request</li><li><a shape="rect" href="bindy.html">Bindy</a> allows to plugin custom formatters for mapping to custom types.</li></ul><p>Fixed these issues:</p><ul><li>Fixed <a shape="rect" href="bean.html">Bean</a> component to avoid ambiguous error for classes t
hat extends generic interface and calling which could lead to falsely duplicate methods (due Java type erasure inserts bridge methods) </li><li>Fixed splitting using tarfile could cause OOME if splitting big files which was mistakenly loaded into memory. Now we work on the tar stream directly.</li><li>Fixed <a shape="rect" href="netty-http.html">Netty HTTP</a> and <a shape="rect" href="netty4-http.html">Netty4 HTTP</a> issue when not specifying a port number then port 80 would not be used but an error about port -1 is not allowed.</li><li>Fixed <a shape="rect" href="swagger-java.html">Swagger Java</a> when using property placeholders in <a shape="rect" href="rest-dsl.html">Rest DSL</a> could cause invalid parameters to be included that was from the placeholder.</li><li>The <code>threads</code> EIP now lets <a shape="rect" href="error-handling-in-camel.html">Error handling in Camel</a> perform redeliveries if the thread pool would oth
erwise reject accepting the task. This allows the error handler to perform redeliveries to attempt to put the task on the thread pool queue, or eventually move the message to a dead letter queue etc.</li><li>Fixed <a shape="rect" href="rest-dsl.html">Rest DSL</a> adding empty header if specifying a non required query parameter that has no default value assigned.</li><li>Fixed <a shape="rect" href="loop.html">doWhile</a> loop which could potentially loop forever.</li><li>Fixed a NPE in <a shape="rect" href="zookeeper.html">Zookeeper</a> consumer if no zookeeper node path was set</li><li>Spring-DM for OSGi moved out of camel-spring into a separate camel-spring-dm module.</li><li>When using continued with <a shape="rect" href="exception-clause.html">onException</a> then dead letter channel endpooint should not be invoked.</li><li>Fixed <a shape="rect" href="error-handler.html">Error Handler</a> to not log exceptions when using <code>continued(true)</code> by default
.</li><li>Fixed so using shareUnitOfWork would now also call specialized <code>AggregationStrategy</code> for onTimeout, onCompletion etc.</li><li>Fixed <a shape="rect" href="jetty.html">Jetty</a> consumer incorrectly handle multipart/form data not being mapped as attachments on the Camel Message.</li><li>Fixed <a shape="rect" href="netty4-http.html">Netty4 HTTP</a> may fail reading the http content from the raw netty stream if the Exchange was routed asynchronously.</li><li>Fixed <a shape="rect" href="netty4-http.html">Netty4 HTTP</a> leak ByteBuf's on the producer side which was not released in all corner cases before they may be gargage collected. </li><li>Fixed <a shape="rect" href="dozer.html">Dozer</a> not able to use variables in mapping files when using OSGi.</li></ul><h3 id="Camel2.18.0Release-New">New <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a></h3><h3 id="Camel2.18.0Release-New.1">New <
a shape="rect" href="components.html">Components</a></h3><ul><li>camel-cm-sms - For sending SMS messages using SM SMS Gateway</li><li><a shape="rect" href="ehcache.html">camel-ehcache</a> - For interacting with Ehcache 3 cache</li><li><a shape="rect" href="flink.html">camel-flink</a> - Bridges Camel connectors with Apache Flink tasks.</li><li>camel-servicenow - For cloud management with ServiceNow</li><li>camel-telegram - For messaging with Telegram</li><li><a shape="rect" href="camel-zipkin.html">camel-zipkin</a> - For tracking Camel message flows/timings using <a shape="rect" class="external-link" href="http://zipkin.io/" style="line-height: 1.42857;" rel="nofollow">zipkin</a></li></ul><h3 id="Camel2.18.0Release-NewDSL">New DSL</h3><ul><li><a shape="rect" href="hystrix-eip.html">hystrix</a> - Using Hystrix as circuit breaker. This requires having <code>camel-hsytrix</code> on the classpath.</li></ul><h3 id="Camel2.18.0Release-NewAnnotations">New Annotations</h3><h3 id="C
amel2.18.0Release-NewDataFormats">New <a shape="rect" href="data-format.html">Data Formats</a></h3><h3 id="Camel2.18.0Release-New.2">New <a shape="rect" href="languages.html">Languages</a></h3><h3 id="Camel2.18.0Release-New.3">New <a shape="rect" href="examples.html">Examples</a></h3><ul><li><code>camel-example-cdi-xml</code>: i<span style="color: rgb(0,0,0);">llustrates the use of Camel XML configuration files into a Camel CDI application</span></li></ul><h3 id="Camel2.18.0Release-New.4">New <a shape="rect" href="tutorials.html">Tutorials</a></h3><h2 id="Camel2.18.0Release-APIbreaking">API breaking</h2><h2 id="Camel2.18.0Release-KnownIssues">Known Issues</h2><h2 id="Camel2.18.0Release-Importantchangestoconsiderwhenupgrading">Important changes to consider when upgrading</h2><ul><li><strong>Java 1.8 is now required.</strong></li><li>Karaf 2.4.x is no longer supported. Karaf 4.x is the primary supported OSGi platform.</li><li>Jetty 8.x is no longer supported and camel-jetty8 has been
removed</li><li>spring 4.0 is no longer supported and camel-test-spring40 has been removed</li><li>spring 3.x is no longer supported</li><li>(only spring-dm using spring 3.2.x as part of camel-spring in osgi/karaf is still in use - but spring-dm is deprecated and we recommend using blueprint)</li><li>Spring-DM for OSGi moved out of camel-spring into a separate camel-spring-dm module. If using Spring XML with Spring-DM then you need to install camel-spring-dm feature in Karaf/ServiceMix.</li><li>The deprecated <code>@LazyLoadTypeConverter</code> has been removed from all <a shape="rect" href="camel-test.html">Camel Test</a> modules</li><li>camel-gae has been removed (was not working anyway)</li><li>The access in the <a shape="rect" href="rest-dsl.html">Rest DSL</a> has been deprecated and no longer in use - its not part of swagger specification anymore.</li><li>Removed the deprecated maven archetypes for SOAP WS using CXF with OSGi Blueprint</li><li>Optimize Camel to o
nly enable AllowUseOriginalMessage if in use by error handler or <a shape="rect" href="oncompletion.html">OnCompletion</a>. End user who manually access the original message using the Java API must configure AllowUseOriginalMessage=true.</li></ul><h2 id="Camel2.18.0Release-GettingtheDistributions">Getting the Distributions</h2><h3 id="Camel2.18.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/x.y.x/apache-camel-x.y.x.zip">apache-cam
el-x.y.x.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/x.y.x/apache-camel-x.y.x.zip.asc">apache-camel-x.y.x.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/x.y.x/apache-camel-x.y.x.tar.gz">apache-camel-x.y.x.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/x.y.x/apache-camel-x.y.x.tar.gz.asc">apache-camel-x.y.x.tar.gz.asc</a></p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">The above URLs use redirection</p><span class="aui-icon aui-icon-small aui-iconfont-in
fo confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using <a shape="rect" class="external-link" href="http://www.mozilla.com/en-US/firefox/" rel="nofollow">FireFox</a></p></div></div><h3 id="Camel2.18.0Release-SourceDistributions">Source 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>Source for Windows</p></td><td colspan="1" rowspan="1" class="conf
luenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x-src.zip">apache-camel-x.y.x-src.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/x.y.x/apache-camel-x.y.x-src.zip.asc">apache-camel-x.y.x-src.zip.asc</a></p></td></tr></tbody></table></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</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/x.y.x/apache-camel-x.y.x-src.tar.gz">apache-camel-x.y.x-src.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/x.y.x/apache-camel-x.y.x-src.tar.
gz.asc">apache-camel-x.y.x-src.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="Camel2.18.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h3><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h1 id="Camel2.18.0Release-Camel2.18.0release(currentlyinprogress)">Camel 2.18.0 release (currently in progress)</h1><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><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"></span></p></div><div style="min-height:200px"> </div><h2 id="Camel2.18.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to the 2.18.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p><ul><li>Added <a shape="rect" href="hystrix-eip.html">Hystrix EIP</a> as EIP pattern that uses native Hystrix as the Circuit Breaker implementation. This requires having <code>camel-hsytrix</code> on the classpath.</li><li>Improved the <a
shape="rect" href="bean.html">Bean</a> component to better match method parameter types when using <a shape="rect" href="simple.html">Simple</a> language as parameter values.</li><li>Added <code>BindyConverter</code> that allows to implement custom data converters for <a shape="rect" href="bindy.html">Bindy</a></li><li>The access in the <a shape="rect" href="rest-dsl.html">Rest DSL</a> has been deprecated and no longer in use - its not part of swagger specification anymore.</li><li><a shape="rect" href="nats.html">Camel-NATS</a> now uses JNATS client instead of the deprecated Java_nats one.</li><li>During startup of <a shape="rect" href="camelcontext.html">CamelContext</a> the services that are used as part of routes are now deferred being started to the end of the startup process. Some IoC frameworks like Spring can otherwise causes a circular dependency issue if services are started too early. A side effect is that if service startup failures happen w
hen being started later, they are now wrapped in the <code>FailedToStartupRouteException</code> to better pin point which route thas the problem.</li><li>Improved the startup sequence of <a shape="rect" href="spring-java-config.html">Spring Java Config</a> to be similar to <a shape="rect" href="spring-boot.html">Spring Boot</a> that helps prevent Spring initialization errors about circular dependencies issues.</li><li>Added PATCH to <a shape="rect" href="rest-dsl.html">Rest DSL</a></li><li>Added "starts with" and "ends with" operator to the <a shape="rect" href="simple.html">Simple</a> language.</li><li>Added <code>BeanIOSplitter</code> to <a shape="rect" href="beanio.html">BeanIO</a> that can be used with the <a shape="rect" href="splitter.html">Splitter</a> EIP to split big payloads in streaming mode without reading the entire content into memory.</li><li>Some of the <a shape="rect" href="aws.html">AWS</a> components allows to specify ARN in
the endpoint configuration. </li><li>The create operation in <a shape="rect" href="zookeeper.html">Zookeeper</a> now creates sub paths if missing.</li><li>Added support for async mode for <a shape="rect" href="servlet.html">SERVLET</a> component to leverage Asynchronous Servlet from the Servlet 3.0 spec.</li><li><a shape="rect" href="bean.html">Bean</a> component and <a shape="rect" href="bean-language.html">Bean Language</a> validates method name must be a valid according to java identifier rules, and also if parameter syntax has an ending parenthesis.</li><li>You can now use <code>@RunWith(CamelSpringBootJUnit4ClassRunner.class)</code> to test Camel <a shape="rect" href="spring-boot.html">Spring Boot</a> applications and use the Camel test annotations from <a shape="rect" href="spring-testing.html">Spring Testing</a> such as <code>@MockEndpoints</code>.</li><li>To turn on logging exhausted message body with the message history you
can configure this easily on the CamelContext level with <code>setLogExhaustedMessageBody</code></li><li><a shape="rect" href="infinispan.html">Camel-Infinispan</a> now supports Aggregation Repository: InfinispanLocalAggregationRepository and InfinispanRemoteAggregationRepository</li><li>The <a shape="rect" href="sql-component.html">SQL Component</a> and <a shape="rect" href="elsql.html">ElSql</a> now supports <code>outputType=StreamList</code> to use an iterator for the output of the SQL query that allows to process the data in a streaming fashion such as with the <a shape="rect" href="splitter.html">Splitter</a> EIP to process the data row by row, and load data from the database as needed.</li><li><a shape="rect" href="jpa.html">JPA</a> now includes a <code>JpaPollingConsumer</code> implementation that better supports <a shape="rect" href="content-enricher.html">Content Enricher</a> using <code>pollEnrich</code> to do a on-demand poll
that returns either none, one or a list of entities as the result. </li><li>Calling <a shape="rect" href="bean.html">Bean</a> with method parameters defined using <a shape="rect" href="simple.html">Simple</a> parameters, now avoids an intermediate conversion of the parameters to a String value. This ensures the passed in values when calling the bean method is using the parameter type as-is from <a shape="rect" href="simple.html">Simple</a>.</li><li><a shape="rect" href="cdi.html">Camel CDI</a> now supports importing Camel XML configuration files</li><li><a shape="rect" href="cdi.html">Camel CDI</a> does not deploy an empty Camel context bean anymore if not route builder beans nor Camel beans are deployed</li><li><a shape="rect" href="cdi.html">Camel CDI</a> adds the <code>@Named</code> qualifier to Camel route management events so that it's possible to observe these events for a specific route with an explicit <code>id</code></li><li><a shape=
"rect" href="beanio.html">Camel BeanIO</a> now supports the possibility to use a custom BeanReaderErrorHandler implementation in his configuration</li><li><a shape="rect" href="kubernetes.html">Camel Kubernetes</a> now supports Kubernetes ConfigMap feature</li><li>The <a shape="rect" href="tokenizer.html">Tokenizer</a> and <a shape="rect" href="xmltokenizer.html">XMLTokenizer</a> language now supports using <a shape="rect" href="simple.html">Simple</a> expressions as the token / xml tag names so they can be dynamic values.</li><li>Added <code>filterDirectory</code> and <code>filterFile</code> options to <a shape="rect" href="file2.html">File2</a> so filtering can be done using <a shape="rect" href="simple.html">Simple</a> language or predicates. </li><li>Optimize Camel to only enable AllowUseOriginalMessage if in use by error handler or <a shape="rect" href="oncompletion.html">OnCompletion</a>. End user who manually access the original message
using the Java API must configure AllowUseOriginalMessage=true.</li><li><a shape="rect" href="ahc.html">Camel-AHC</a> now support a connectionClose parameter to allow explicitly adding a Connection Close header to HTTP request</li><li><a shape="rect" href="http.html">Camel-HTTP</a> now support a connectionClose parameter to allow explicitly adding a Connection Close header to HTTP request</li><li><a shape="rect" href="http4.html">Camel-HTTP4</a> now support a connectionClose parameter to allow explicitly adding a Connection Close header to HTTP request</li><li><a shape="rect" href="jetty.html">Camel-Jetty</a> now support a connectionClose parameter to allow explicitly adding a Connection Close header to HTTP request</li><li><a shape="rect" href="bindy.html">Bindy</a> allows to plugin custom formatters for mapping to custom types.</li></ul><p>Fixed these issues:</p><ul><li>Fixed <a shape="rect" href="bean.html">Bean</a> component to avoid ambiguous error for classes t
hat extends generic interface and calling which could lead to falsely duplicate methods (due Java type erasure inserts bridge methods) </li><li>Fixed splitting using tarfile could cause OOME if splitting big files which was mistakenly loaded into memory. Now we work on the tar stream directly.</li><li>Fixed <a shape="rect" href="netty-http.html">Netty HTTP</a> and <a shape="rect" href="netty4-http.html">Netty4 HTTP</a> issue when not specifying a port number then port 80 would not be used but an error about port -1 is not allowed.</li><li>Fixed <a shape="rect" href="swagger-java.html">Swagger Java</a> when using property placeholders in <a shape="rect" href="rest-dsl.html">Rest DSL</a> could cause invalid parameters to be included that was from the placeholder.</li><li>The <code>threads</code> EIP now lets <a shape="rect" href="error-handling-in-camel.html">Error handling in Camel</a> perform redeliveries if the thread pool would oth
erwise reject accepting the task. This allows the error handler to perform redeliveries to attempt to put the task on the thread pool queue, or eventually move the message to a dead letter queue etc.</li><li>Fixed <a shape="rect" href="rest-dsl.html">Rest DSL</a> adding empty header if specifying a non required query parameter that has no default value assigned.</li><li>Fixed <a shape="rect" href="loop.html">doWhile</a> loop which could potentially loop forever.</li><li>Fixed a NPE in <a shape="rect" href="zookeeper.html">Zookeeper</a> consumer if no zookeeper node path was set</li><li>Spring-DM for OSGi moved out of camel-spring into a separate camel-spring-dm module.</li><li>When using continued with <a shape="rect" href="exception-clause.html">onException</a> then dead letter channel endpooint should not be invoked.</li><li>Fixed <a shape="rect" href="error-handler.html">Error Handler</a> to not log exceptions when using <code>continued(true)</code> by default
.</li><li>Fixed so using shareUnitOfWork would now also call specialized <code>AggregationStrategy</code> for onTimeout, onCompletion etc.</li><li>Fixed <a shape="rect" href="jetty.html">Jetty</a> consumer incorrectly handle multipart/form data not being mapped as attachments on the Camel Message.</li><li>Fixed <a shape="rect" href="netty4-http.html">Netty4 HTTP</a> may fail reading the http content from the raw netty stream if the Exchange was routed asynchronously.</li><li>Fixed <a shape="rect" href="netty4-http.html">Netty4 HTTP</a> leak ByteBuf's on the producer side which was not released in all corner cases before they may be gargage collected. </li><li>Fixed <a shape="rect" href="dozer.html">Dozer</a> not able to use variables in mapping files when using OSGi.</li></ul><h3 id="Camel2.18.0Release-New">New <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a></h3><h3 id="Camel2.18.0Release-New.1">New <
a shape="rect" href="components.html">Components</a></h3><ul><li>camel-cm-sms - For sending SMS messages using SM SMS Gateway</li><li><a shape="rect" href="ehcache.html">camel-ehcache</a> - For interacting with Ehcache 3 cache</li><li><a shape="rect" href="flink.html">camel-flink</a> - Bridges Camel connectors with Apache Flink tasks.</li><li>camel-servicenow - For cloud management with ServiceNow</li><li>camel-telegram - For messaging with Telegram</li><li><a shape="rect" href="camel-zipkin.html">camel-zipkin</a> - For tracking Camel message flows/timings using <a shape="rect" class="external-link" href="http://zipkin.io/" style="line-height: 1.42857;" rel="nofollow">zipkin</a></li><li><a shape="rect" href="consul-component.html">camel-consul</a> - F<span>or integrating your application with <a shape="rect" class="external-link" href="https://www.consul.io" rel="nofollow">Consul</a></span></li></ul><h3 id="Camel2.18.0Release-NewDSL">New DSL</h3><ul><li><a shape="rect" hre
f="hystrix-eip.html">hystrix</a> - Using Hystrix as circuit breaker. This requires having <code>camel-hsytrix</code> on the classpath.</li></ul><h3 id="Camel2.18.0Release-NewAnnotations">New Annotations</h3><h3 id="Camel2.18.0Release-NewDataFormats">New <a shape="rect" href="data-format.html">Data Formats</a></h3><h3 id="Camel2.18.0Release-New.2">New <a shape="rect" href="languages.html">Languages</a></h3><h3 id="Camel2.18.0Release-New.3">New <a shape="rect" href="examples.html">Examples</a></h3><ul><li><code>camel-example-cdi-xml</code>: i<span style="color: rgb(0,0,0);">llustrates the use of Camel XML configuration files into a Camel CDI application</span></li></ul><h3 id="Camel2.18.0Release-New.4">New <a shape="rect" href="tutorials.html">Tutorials</a></h3><h2 id="Camel2.18.0Release-APIbreaking">API breaking</h2><h2 id="Camel2.18.0Release-KnownIssues">Known Issues</h2><h2 id="Camel2.18.0Release-Importantchangestoconsiderwhenupgrading">Important changes to consider when upgra
ding</h2><ul><li><strong>Java 1.8 is now required.</strong></li><li>Karaf 2.4.x is no longer supported. Karaf 4.x is the primary supported OSGi platform.</li><li>Jetty 8.x is no longer supported and camel-jetty8 has been removed</li><li>spring 4.0 is no longer supported and camel-test-spring40 has been removed</li><li>spring 3.x is no longer supported</li><li>(only spring-dm using spring 3.2.x as part of camel-spring in osgi/karaf is still in use - but spring-dm is deprecated and we recommend using blueprint)</li><li>Spring-DM for OSGi moved out of camel-spring into a separate camel-spring-dm module. If using Spring XML with Spring-DM then you need to install camel-spring-dm feature in Karaf/ServiceMix.</li><li>The deprecated <code>@LazyLoadTypeConverter</code> has been removed from all <a shape="rect" href="camel-test.html">Camel Test</a> modules</li><li>camel-gae has been removed (was not working anyway)</li><li>The access in the <a shape="rect" href="rest-dsl.html"
>Rest DSL</a> has been deprecated and no longer in use - its not part of swagger specification anymore.</li><li>Removed the deprecated maven archetypes for SOAP WS using CXF with OSGi Blueprint</li><li>Optimize Camel to only enable AllowUseOriginalMessage if in use by error handler or <a shape="rect" href="oncompletion.html">OnCompletion</a>. End user who manually access the original message using the Java API must configure AllowUseOriginalMessage=true.</li></ul><h2 id="Camel2.18.0Release-GettingtheDistributions">Getting the Distributions</h2><h3 id="Camel2.18.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/x.y.x/apache-camel-x.y.x.zip">apache-camel-x.y.x.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/x.y.x/apache-camel-x.y.x.zip.asc">apache-camel-x.y.x.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/x.y.x/apache-camel-x.y.x.tar.gz">apache-camel-x.y.x.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/x.y.x/apache-camel-x.y.x.tar.gz.asc">apache-camel-x.y.x.tar.gz.asc</a><
/p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">The above URLs use redirection</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using <a shape="rect" class="external-link" href="http://www.mozilla.com/en-US/firefox/" rel="nofollow">FireFox</a></p></div></div><h3 id="Camel2.18.0Release-SourceDistributions">Source 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>Source for Windows</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/x.y.x/apache-camel-x.y.x-src.zip">apache-camel-x.y.x-src.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/x.y.x/apache-camel-x.y.x-src.zip.asc">apache-camel-x.y.x-src.zip.asc</a></p></td></tr></tbody></table></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</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/x.y.x/apache-camel-x.y.x-src.tar.
gz">apache-camel-x.y.x-src.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/x.y.x/apache-camel-x.y.x-src.tar.gz.asc">apache-camel-x.y.x-src.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="Camel2.18.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h3><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-core</artifactId>
Modified: websites/production/camel/content/component-list.html
==============================================================================
--- websites/production/camel/content/component-list.html (original)
+++ websites/production/camel/content/component-list.html Tue May 24 11:19:43 2016
@@ -167,7 +167,9 @@
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses the <a shape="rect" class="external-link" href="http://chemistry.apache.org/java/opencmis.html">Apache Chemistry</a> client API to interface with CMIS supporting CMS</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cometd.html">Cometd</a> / camel-cometd</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cometd://hostName:port/channelName[?options]
]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="context.html">Context</a> / camel-context</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>Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="consul-component.html">Consul</a> / camel-consul</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[consul:apiEndpoint[?options]]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><span>For interfacing with an </span><span> </span><a shape="rect" class="external-link" href="https://www.consul.io/" rel="nofollow">Consul</a>.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="context.html">Context</a> / camel-context</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[context:camelContextId:localEndpointName[?options]
]]></script>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to refer to endpoints within a separate CamelContext to provide a simple <a shape="rect" href="context.html">black box composition</a> approach so that routes can be combined into a CamelContext and then used as a black box component inside other routes in other CamelContexts</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="controlbus-component.html">ControlBus</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
Modified: websites/production/camel/content/component.html
==============================================================================
--- websites/production/camel/content/component.html (original)
+++ websites/production/camel/content/component.html Tue May 24 11:19:43 2016
@@ -168,7 +168,9 @@
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses the <a shape="rect" class="external-link" href="http://chemistry.apache.org/java/opencmis.html">Apache Chemistry</a> client API to interface with CMIS supporting CMS</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cometd.html">Cometd</a> / camel-cometd</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cometd://hostName:port/channelName[?options]
]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="context.html">Context</a> / camel-context</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>Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="consul-component.html">Consul</a> / camel-consul</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[consul:apiEndpoint[?options]]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><span>For interfacing with an </span><span> </span><a shape="rect" class="external-link" href="https://www.consul.io/" rel="nofollow">Consul</a>.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="context.html">Context</a> / camel-context</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[context:camelContextId:localEndpointName[?options]
]]></script>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to refer to endpoints within a separate CamelContext to provide a simple <a shape="rect" href="context.html">black box composition</a> approach so that routes can be combined into a CamelContext and then used as a black box component inside other routes in other CamelContexts</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="controlbus-component.html">ControlBus</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 Tue May 24 11:19:43 2016
@@ -168,7 +168,9 @@
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses the <a shape="rect" class="external-link" href="http://chemistry.apache.org/java/opencmis.html">Apache Chemistry</a> client API to interface with CMIS supporting CMS</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cometd.html">Cometd</a> / camel-cometd</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cometd://hostName:port/channelName[?options]
]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="context.html">Context</a> / camel-context</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>Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="consul-component.html">Consul</a> / camel-consul</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[consul:apiEndpoint[?options]]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><span>For interfacing with an </span><span> </span><a shape="rect" class="external-link" href="https://www.consul.io/" rel="nofollow">Consul</a>.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="context.html">Context</a> / camel-context</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: plain; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[context:camelContextId:localEndpointName[?options]
]]></script>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to refer to endpoints within a separate CamelContext to provide a simple <a shape="rect" href="context.html">black box composition</a> approach so that routes can be combined into a CamelContext and then used as a black box component inside other routes in other CamelContexts</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="controlbus-component.html">ControlBus</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">