Author: buildbot
Date: Wed May 18 08:19:44 2016
New Revision: 988517
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/ahc.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-2180-release.html
websites/production/camel/content/http4.html
Modified: websites/production/camel/content/ahc.html
==============================================================================
--- websites/production/camel/content/ahc.html (original)
+++ websites/production/camel/content/ahc.html Wed May 18 08:19:44 2016
@@ -98,13 +98,7 @@
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ahc:http://hostname[:port][/resourceUri][?options]
ahc:https://hostname[:port][/resourceUri][?options]
]]></script>
-</div></div><p>Will by default use port 80 for HTTP and 443 for
HTTPS.</p><p>You can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="AHC-AhcEndpointOptions">AhcEndpoint Options</h3><div
class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>throwExceptionOnFailure</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Option to disable throwing the
<code>AhcOperationFailedException</code> in case of failed responses from the
remote server. This allows you to get all responses regardless of the HTTP
status code. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>bridgeEndpoint</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> If the option is true, then
the Ex
change.HTTP_URI header is ignored, and use the endpoint's URI for request. You
may also set the <strong>throwExcpetionOnFailure</strong> to be false to let
the AhcProducer send all the fault response back. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>transferException</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>false</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> If enabled and an <a shape="rect"
href="exchange.html">Exchange</a> failed processing on the consumer side, and
if the caused <code>Exception</code> was send back serialized in the response
as a <code>application/x-java-serialized-object</code> content type (for
example using <a shape="rect" href="jetty.html">Jetty</a> or <a shape="rect"
href="servlet.html">Servlet</a> Camel components). On the producer side the
exception will be deserialized and thrown as is, instead of the
<code>AhcOperationFailedException</code>. The caused exception is
required to be serialized. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>client</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> To use a custom
<code>com.ning.http.client.AsyncHttpClient</code>. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>clientConfig</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To configure the
<code>AsyncHttpClient</code> to use a custom
<code>com.ning.http.client.AsyncHttpClientConfig</code> instance. This
instance replaces any instance configured at the component level.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>clientConfig.x</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1"
class="confluen
ceTd"><p> To configure additional properties of the
<code>com.ning.http.client.AsyncHttpClientConfig</code> instance used by the
endpoint. Note that configuration options set using this parameter will be
merged with those set using the <code>clientConfig</code> parameter or the
instance set at the component level with properties set using this parameter
taking priority. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>clientConfig.realm.x</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong>
To configure realm properties of the
<code>com.ning.http.client.AsyncHttpClientConfig</code> The options which can
be used are the options from
<code>com.ning.http.client.Realm.RealmBuilder</code>. eg to set scheme, you can
configure <code>"clientConfig.realm.scheme=DIGEST"</code> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluence
Td"><p> <code>binding</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> To use a custom
<code>org.apache.camel.component.ahc.AhcBinding</code>. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>sslContextParameters</code> <br clear="none" class="atl-forced-newline">
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code>
<br clear="none" class="atl-forced-newline"> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9:</strong> Reference to a
<code>org.apache.camel.util.jsse.SSLContextParameters</code> in the <a
shape="rect" href="registry.html">Registry</a>.  This reference overrides
any configured SSLContextParameters at the component level.  See <a
shape="rect" href="#AHC-UsingtheJSSEConfigurationUtility">Using the JSSE
Configuration Utility</a>.  Note that configuring this option will overri
de any SSL/TLS configuration options provided through the clientConfig option
at the endpoint or component level. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>bufferSize</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>4096</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.10.3:</strong>
The initial in-memory buffer size used when transferring data between Camel and
AHC Client. </p></td></tr></tbody></table></div>
-</div><h3 id="AHC-AhcComponentOptions">AhcComponent Options</h3><div
class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>client</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a custom
<code>com.ning.http.client.AsyncHttpClient</code>. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>clientConfig</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To configure the
<code>AsyncHttpClient</code> to use a custom
<code>com.ning.http.client.AsyncHttpClientConfig</code>. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd
"><p> <code>binding</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> To use a custom
<code>org.apache.camel.component.ahc.AhcBinding</code>. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>sslContextParameters</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.9:</strong> To configure custom
SSL/TLS configuration options at the component level.  See  <a
shape="rect" href="#AHC-UsingtheJSSEConfigurationUtility">Using the JSSE
Configuration Utility</a> for more details.  Note that configuring this
option will override any SSL/TLS configuration options provided through the
clientConfig option at the endpoint or component level.
</p></td></tr></tbody></table></div>
-</div><p>Notice that setting any of the options on the
<code>AhcComponent</code> will propagate those options to <code>AhcEndpoint}}s
being created. However the {{AhcEndpoint</code> can also configure/override a
custom option. Options set on endpoints will always take precedence over
options from the <code>AhcComponent</code>.</p><h3
id="AHC-MessageHeaders">Message Headers</h3><div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>Exchange.HTTP_URI</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>String</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> URI to call. Will override existing URI set directly
on the endpoint. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>Exchange.HTTP_PATH</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Request URI's
path, the header will be used to build the request URI with the HTTP_URI. If
the path is start with "/", http producer will try to find the relative path b
ased on the Exchange.HTTP_BASE_URI header or the
<code>exchange.getFromEndpoint().getEndpointUri();</code> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>Exchange.HTTP_QUERY</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11 onwards:</strong> URI
parameters. Will override existing URI parameters set directly on the endpoint.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>Exchange.HTTP_RESPONSE_CODE</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The HTTP response code from the external server. Is
200 for OK. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>Exchange.HTTP_CHARACTER_ENCODING</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>String</code> </p><
/td><td colspan="1" rowspan="1" class="confluenceTd"><p> Character encoding.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>Exchange.CONTENT_TYPE</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> The HTTP content type. Is set on both the
IN and OUT message to provide a content type, such as <code>text/html</code>.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>Exchange.CONTENT_ENCODING</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> The HTTP content encoding. Is set on both
the IN and OUT message to provide a content encoding, such as
<code>gzip</code>. </p></td></tr></tbody></table></div>
-</div><h3 id="AHC-MessageBody">Message Body</h3><p>Camel will store the HTTP
response from the external server on the OUT body. All headers from the IN
message will be copied to the OUT message, so headers are preserved during
routing. Additionally Camel will add the HTTP response headers as well to the
OUT message headers.</p><h3 id="AHC-Responsecode">Response code</h3><p>Camel
will handle according to the HTTP response code:</p><ul
class="alternate"><li>Response code is in the range 100..299, Camel regards it
as a success response.</li><li>Response code is in the range 300..399, Camel
regards it as a redirection response and will throw a
<code>AhcOperationFailedException</code> with the
information.</li><li><p>Response code is 400+, Camel regards it as an external
server failure and will throw a <code>AhcOperationFailedException</code> with
the information.</p><div class="confluence-information-macro
confluence-information-macro-tip"><p
class="title">throwExceptionOnFailure</p><sp
an class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The option,
<code>throwExceptionOnFailure</code>, can be set to <code>false</code> to
prevent the <code>AhcOperationFailedException</code> from being thrown for
failed response codes. This allows you to get any response from the remote
server.</p></div></div></li></ul><h3
id="AHC-AhcOperationFailedException">AhcOperationFailedException</h3><p>This
exception contains the following information:</p><ul class="alternate"><li>The
HTTP status code</li><li>The HTTP status line (text of the status
code)</li><li>Redirect location, if server returned a redirect</li><li>Response
body as a <code>java.lang.String</code>, if server provided a body as
response</li></ul><h3 id="AHC-CallingusingGETorPOST">Calling using GET or
POST</h3><p>The following algorithm is used to determine if either
<code>GET</code> or <code>POST</code> HTTP method should be used
:<br clear="none"> 1. Use method provided in header.<br clear="none"> 2.
<code>GET</code> if query string is provided in header.<br clear="none"> 3.
<code>GET</code> if endpoint is configured with a query string.<br
clear="none"> 4. <code>POST</code> if there is data to send (body is not
null).<br clear="none"> 5. <code>GET</code> otherwise.</p><h3
id="AHC-ConfiguringURItocall">Configuring URI to call</h3><p>You can set the
HTTP producer's URI directly form the endpoint URI. In the route below, Camel
will call out to the external server, <code>oldhost</code>, using HTTP.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>Will by default use port 80 for HTTP and 443 for
HTTPS.</p><p>You can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="AHC-AhcEndpointOptions">AhcEndpoint Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>throwExceptionOnFailure</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Option to disable throwing the
<code>AhcOperationFailedException</code> in case of failed responses from the
remote server. This allows you to get all responses regardless of the HTTP
status code.<
/p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>bridgeEndpoint</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>If the option is true, then the
Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request.
You may also set the <strong>throwExcpetionOnFailure</strong> to be false to
let the AhcProducer send all the fault response back.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>transferException</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>If enabled and an <a shape="rect"
href="exchange.html">Exchange</a> failed processing on the consumer side, and
if the caused <code>Exception</code> was send back serialized in the response
as a <code>application/x-java-serialized-object</code> content type (for
example using <a sh
ape="rect" href="jetty.html">Jetty</a> or <a shape="rect"
href="servlet.html">SERVLET</a> Camel components). On the producer side the
exception will be deserialized and thrown as is, instead of the
<code>AhcOperationFailedException</code>. The caused exception is required to
be serialized.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>client</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>To use a custom
<code>com.ning.http.client.AsyncHttpClient</code>.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>clientConfig</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>To configure the
<code>AsyncHttpClient</code> to use a custom
<code>com.ning.http.client.AsyncHttpClientConfig</code> instance. This instance
replaces any instance configured at t
he component level.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>clientConfig.x</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>To configure additional properties of the
<code>com.ning.http.client.AsyncHttpClientConfig</code> instance used by the
endpoint. Note that configuration options set using this parameter will be
merged with those set using the <code>clientConfig</code> parameter or the
instance set at the component level with properties set using this parameter
taking priority.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>clientConfig.realm.x</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> To
configure realm properties of the
<code>com.ning.http.client.AsyncHttpClientConfig</code> The options whic
h can be used are the options from
<code>com.ning.http.client.Realm.RealmBuilder</code>. eg to set scheme, you can
configure <code>"clientConfig.realm.scheme=DIGEST"</code></p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>binding</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>To use a custom
<code>org.apache.camel.component.ahc.AhcBinding</code>.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>sslContextParameters</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.9:</strong>
Reference to a <code>org.apache.camel.util.jsse.SSLContextParameters</code> in
the <a shape="rect" href="registry.html">Registry</a>.  This reference
overrides any configured SSLContextParameters at the component level.  See
<a shape="rect" href
="#AHC-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration
Utility</a>.  Note that configuring this option will override any SSL/TLS
configuration options provided through the clientConfig option at the endpoint
or component level.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>bufferSize</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>4096</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.10.3:</strong> The initial
in-memory buffer size used when transferring data between Camel and AHC
Client.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>connectionClose</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><strong>Camel
2.18: </strong></strong>If this option is true, the producer will add a
Connection Close header to HTTP Request</p></td></tr></tbod
y></table></div></div><h3 id="AHC-AhcComponentOptions">AhcComponent
Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>client</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>To use a custom
<code>com.ning.http.client.AsyncHttpClient</code>.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>clientConfig</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>To configure the
<code>AsyncHttpClient</code> to use a custom <code>com.ning.http.clien
t.AsyncHttpClientConfig</code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>binding</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>To use a custom
<code>org.apache.camel.component.ahc.AhcBinding</code>.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>sslContextParameters</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.9:</strong> To
configure custom SSL/TLS configuration options at the component level. 
See  <a shape="rect" href="#AHC-UsingtheJSSEConfigurationUtility">Using
the JSSE Configuration Utility</a> for more details.  Note that
configuring this option will override any SSL/TLS configuration options
provided through the clientConfig option at the endpoint or component
level.</p></td></tr></tbody>
</table></div></div><p>Notice that setting any of the options on the
<code>AhcComponent</code> will propagate those options to <code>AhcEndpoint}}s
being created. However the {{AhcEndpoint</code> can also configure/override a
custom option. Options set on endpoints will always take precedence over
options from the <code>AhcComponent</code>.</p><h3
id="AHC-MessageHeaders">Message Headers</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>Exchange.HTTP_URI</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>URI to call. Will override
existing URI set directly on the endpoint.
</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>Exchange.HTTP_PATH</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Request URI's path, the header will be used
to build the request URI with the HTTP_URI. If the path is start with "/", http
producer will try to find the relative path based on the Exchange.HTTP_BASE_URI
header or the
<code>exchange.getFromEndpoint().getEndpointUri();</code></p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>Exchange.HTTP_QUERY</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11
onwards:</strong> URI parameters. Will override existing URI parameters set
directly on the endpoint.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>Exchange.HTTP_RESPONSE_CODE</code></p></t
d><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>The HTTP response code from the external server. Is 200
for OK.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>Exchange.HTTP_CHARACTER_ENCODING</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Character encoding.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>Exchange.CONTENT_TYPE</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The HTTP content type. Is set
on both the IN and OUT message to provide a content type, such as
<code>text/html</code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>Exchange.CONTENT_ENCODING</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd
"><p><code>String</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>The HTTP content encoding. Is set on both the IN and
OUT message to provide a content encoding, such as
<code>gzip</code>.</p></td></tr></tbody></table></div></div><h3
id="AHC-MessageBody">Message Body</h3><p>Camel will store the HTTP response
from the external server on the OUT body. All headers from the IN message will
be copied to the OUT message, so headers are preserved during routing.
Additionally Camel will add the HTTP response headers as well to the OUT
message headers.</p><h3 id="AHC-Responsecode">Response code</h3><p>Camel will
handle according to the HTTP response code:</p><ul
class="alternate"><li>Response code is in the range 100..299, Camel regards it
as a success response.</li><li>Response code is in the range 300..399, Camel
regards it as a redirection response and will throw a
<code>AhcOperationFailedException</code> with the
information.</li><li><p>Response code is 400+, Camel reg
ards it as an external server failure and will throw a
<code>AhcOperationFailedException</code> with the information.</p><div
class="confluence-information-macro confluence-information-macro-tip"><p
class="title">throwExceptionOnFailure</p><span class="aui-icon aui-icon-small
aui-iconfont-approve confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The option,
<code>throwExceptionOnFailure</code>, can be set to <code>false</code> to
prevent the <code>AhcOperationFailedException</code> from being thrown for
failed response codes. This allows you to get any response from the remote
server.</p></div></div></li></ul><h3
id="AHC-AhcOperationFailedException">AhcOperationFailedException</h3><p>This
exception contains the following information:</p><ul class="alternate"><li>The
HTTP status code</li><li>The HTTP status line (text of the status
code)</li><li>Redirect location, if server returned a redirect</li><li>Response
body as a <code>java.lang.String
</code>, if server provided a body as response</li></ul><h3
id="AHC-CallingusingGETorPOST">Calling using GET or POST</h3><p>The following
algorithm is used to determine if either <code>GET</code> or <code>POST</code>
HTTP method should be used:<br clear="none"> 1. Use method provided in
header.<br clear="none"> 2. <code>GET</code> if query string is provided in
header.<br clear="none"> 3. <code>GET</code> if endpoint is configured with a
query string.<br clear="none"> 4. <code>POST</code> if there is data to send
(body is not null).<br clear="none"> 5. <code>GET</code> otherwise.</p><h3
id="AHC-ConfiguringURItocall">Configuring URI to call</h3><p>You can set the
HTTP producer's URI directly form the endpoint URI. In the route below, Camel
will call out to the external server, <code>oldhost</code>, using HTTP.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("direct:start")
.to("ahc:http://oldhost");
]]></script>
@@ -183,7 +177,7 @@ AhcComponent component = context.getComp
// and set our custom client config to be used
component.setClientConfig(config);
]]></script>
-</div></div><p>In Camel <strong>2.9</strong>, the AHC component uses Async
HTTP library 1.6.4. This newer version provides added support for plain bean
style configuration. The <code>AsyncHttpClientConfigBean</code> class provides
getters and setters for the configuration options available in
<code>AsyncHttpClientConfig</code>. An instance of
<code>AsyncHttpClientConfigBean</code> may be passed directly to the AHC
component or referenced in an endpoint URI using the <code>clientConfig</code>
URI parameter.</p><p>Also available in Camel <strong>2.9</strong> is the
ability to set configuration options directly in the URI. URI parameters
starting with "clientConfig." can be used to set the various configurable
properties of <code>AsyncHttpClientConfig</code>. The properties specified in
the endpoint URI are merged with those specified in the configuration
referenced by the "clientConfig" URI parameter with those being set using the
"clientConfig." parameter taking priority. The <code>A
syncHttpClientConfig</code> instance referenced is always copied for each
endpoint such that settings on one endpoint will remain independent of settings
on any previously created endpoints. The example below shows how to configure
the AHC component using the "clientConfig." type URI parameters.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div>In Camel <strong>2.9</strong>, the AHC component uses Async HTTP
library 1.6.4. This newer version provides added support for plain bean style
configuration. The <code>AsyncHttpClientConfigBean</code> class provides
getters and setters for the configuration options available in
<code>AsyncHttpClientConfig</code>. An instance of
<code>AsyncHttpClientConfigBean</code> may be passed directly to the AHC
component or referenced in an endpoint URI using the <code>clientConfig</code>
URI parameter.<p>Also available in Camel <strong>2.9</strong> is the ability to
set configuration options directly in the URI. URI parameters starting with
"clientConfig." can be used to set the various configurable properties of
<code>AsyncHttpClientConfig</code>. The properties specified in the endpoint
URI are merged with those specified in the configuration referenced by the
"clientConfig" URI parameter with those being set using the "clientConfig."
parameter taking priority. The <code>AsyncHtt
pClientConfig</code> instance referenced is always copied for each endpoint
such that settings on one endpoint will remain independent of settings on any
previously created endpoints. The example below shows how to configure the AHC
component using the "clientConfig." type URI parameters.</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("direct:start")
.to("ahc:http://localhost:8080/foo?clientConfig.maxRequestRetry=3&clientConfig.followRedirects=true")
]]></script>
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 Wed May 18
08:19:44 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></ul><p>Fixed these
issues:</p><ul><li>Fixed <a shape="rect" href="bean.html">Bean</a>
component to avoid ambiguous error for classes that 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 fro
m 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 otherwise 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 m
apping 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="flink.html">camel-flink</a> - Bridges Camel connectors with Apache Flink
tasks.</li><li><a shape="rect" href="hystrix.html">camel-hystrix</a> - For
implementing circuit breaker, timeouts, bulkheads, caching,
etc.</li><li>camel-servicenow - For cloud management with ServiceNow</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="ehcache.html">camel-ehcache</a> - For interacting with Ehcache 3
cache</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="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-Importan
tchangestoconsiderwhenupgrading">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 an
yway)</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 downl
oad</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-came
l/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></t
h><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.apach
e.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></ul><p>Fixed these
issues:</p><ul><li>Fixed <a shape="rect" href="bean.html">Bean</a>
component to avoid ambiguous error for classes that extends generic interface
and calling which could lead to falsely duplicate methods (due Java type
erasure inserts br
idge 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
otherwise 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 o
nTimeout, 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 Gat
eway</li><li><a shape="rect" href="flink.html">camel-flink</a> - Bridges Camel
connectors with Apache Flink tasks.</li><li><a shape="rect"
href="hystrix.html">camel-hystrix</a> - For implementing circuit breaker,
timeouts, bulkheads, caching, etc.</li><li>camel-servicenow - For cloud
management with ServiceNow</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="ehcache.html">camel-ehcache</a> - For interacting with Ehcache 3
cache</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="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 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 s
upported 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"></s
pan><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="exter
nal-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"><
![http://camel.apache.org/download.data/camel-box-v1.0-150x200.png"](http://camel.apache.org/download.data/camel-box-v1.0-150x200.png"){kind=link}