svn commit: r1042911 [34/48] - in /websites/production/camel/content: ./ 2007/08/17/ 2008/04/08/ 2008/04/28/ 2009/01/19/ 2009/10/26/ 2012/01/17/ 2012/03/01/ 2019/03/ 2019/03/31/

[bu...@apache.org]

Modified: websites/production/camel/content/mina2.html
==============================================================================
--- websites/production/camel/content/mina2.html (original)
+++ websites/production/camel/content/mina2.html Sun Mar 31 15:23:07 2019
@@ -88,7 +88,7 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="MINA2-MINA2Component">MINA 2 Component</h2><p><strong>Available as of Camel 2.10</strong></p><p>The <strong>mina2:</strong> component is a transport for working with <a shape="rect" class="external-link" href="http://mina.apache.org/">Apache MINA 2.x</a></p><div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>Favor using <a shape="rect" href="netty.html">Netty</a> as Netty is a much more active maintained and popular project than Apache Mina currently is</p></div></div><div class="confluence-information-macro confluence-information-macro-information conf-macro output-block" data-hasbody="true" data-macro-name="info"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon
 "> </span><div class="confluence-information-macro-body"><p>Be careful with sync=false on consumer endpoints. Since camel-mina2 all consumer exchanges are InOut. This is different to camel-mina.</p></div></div><p>&#160;</p><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="MINA2-MINA2Component">MINA 2 Component</h2><p><strong>Available as of Camel 2.10</strong></p><p>The <strong>mina2:</strong> component is a transport for working with <a shape="rect" class="external-link" href="http://mina.apache.org/">Apache MINA 2.x</a></p><div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>Favor using <a shape="rect" href="netty.html">Netty</a> as Netty is a much more active maintained and popular project than Apache Mina currently is</p></div></div><div class="confluence-information-macro confluence-information-macro-information conf-macro output-block" data-hasbody="true" data-macro-name="info"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon
 "> </span><div class="confluence-information-macro-body"><p>Be careful with sync=false on consumer endpoints. Since camel-mina2 all consumer exchanges are InOut. This is different to camel-mina.</p></div></div><p>&#160;</p><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-mina2&lt;/artifactId&gt;
@@ -96,7 +96,7 @@
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 </pre>
-</div></div><h3 id="MINA2-URIformat">URI format</h3><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="MINA2-URIformat">URI format</h3><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">mina2:tcp://hostname[:port][?options]
 mina2:udp://hostname[:port][?options]
 mina2:vm://hostname[:port][?options]
@@ -104,10 +104,10 @@ mina2:vm://hostname[:port][?options]
 </div></div><p>You can specify a codec in the <a shape="rect" href="registry.html">Registry</a> using the <strong>codec</strong> option. If you are using TCP and no codec is specified then the <code>textline</code> flag is used to determine if text line based codec or object serialization should be used instead. By default the object serialization is used.</p><p>For UDP if no codec is specified the default uses a basic <code>ByteBuffer</code> based codec.</p><p>The VM protocol is used as a direct forwarding mechanism in the same JVM.</p><p>A Mina producer has a default timeout value of 30 seconds, while it waits for a response from the remote server.</p><p>In normal use, <code>camel-mina</code> only supports marshalling the body content&#8212;message headers and exchange properties are not sent.<br clear="none"> However, the option, <strong>transferExchange</strong>, does allow you to transfer the exchange itself over the wire. See options below.</p><p>You can append query options t
 o the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p><h3 id="MINA2-Options">Options</h3><div class="confluenceTableSmall conf-macro output-block" data-hasbody="true" data-macro-name="div"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default 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>codec</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can refer to a named <code>ProtocolCodecFactory</code> instance in your <a shape="rect" href="registry.html">Registry</a> such as your Spring <code>ApplicationContext</code>, which is then used for the marshalling.</p></td></tr><tr><td colspan="1" rowspan="1" class="conf
 luenceTd"><p><code>disconnect</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether or not to disconnect(close) from Mina session right after use. Can be used for both consumer and producer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>textline</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Only used for TCP. If no codec is specified, you can use this flag to indicate a text line based codec; if not specified or the value is <code>false</code>, then Object Serialization is assumed over TCP.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>textlineDelimiter</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>DEFAULT</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Only used for TCP and if <stron
 g>textline=true</strong>. Sets the text line delimiter to use. Possible values are: <code>DEFAULT</code>, <code>AUTO</code>, <code>WINDOWS</code>, <code>UNIX</code> or <code>MAC</code>. If none provided, Camel will use <code>DEFAULT</code>. This delimiter is used to mark the end of text.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>sync</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Setting to set endpoint as one-way or request-response.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>lazySessionCreation</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sessions can be lazily created to avoid exceptions, if the remote server is not up and running when the Camel producer is started.</p></td></tr><tr><td colspan="1" rowspan="1" class="conf
 luenceTd"><p><code>timeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can configure the timeout that specifies how long to wait for a response from a remote server. The timeout unit is in milliseconds, so 60000 is 60 seconds. The timeout is only used for Mina producer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>encoding</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><em>JVM Default</em></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can configure the encoding (a <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/java/nio/charset/Charset.html" rel="nofollow">charset name</a>) to use for the TCP textline codec and the UDP protocol. If not provided, Camel will use the <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/java/nio/charset/Charset.html#
 defaultCharset()" rel="nofollow">JVM default Charset</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transferExchange</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Only used for TCP. You can transfer the exchange over the wire instead of just the body. The following fields are transferred: In body, Out body, fault body, In headers, Out headers, fault headers, exchange properties, exchange exception. This requires that the objects are <em>serializable</em>. Camel will exclude any non-serializable objects and log it at <code>WARN</code> level.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>minaLogger</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can enable the Apache MINA logging filter. Apache MINA uses <code>slf4j</code> lo
 gging at <code>INFO</code> level to log all input and output.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>filters</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can set a list of <a shape="rect" class="external-link" href="http://mina.apache.org/iofilter.html">Mina IoFilters</a> to register. The <code>filters</code> can be specified as a comma-separate list of bean references (e.g. <code>#filterBean1,#filterBean2</code>) where each bean must be of type <code>org.apache.mina.common.IoFilter</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>encoderMaxLineLength</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Set the textline protocol encoder max line length. By default the default value of Mina itself is used which are <code>Int
 eger.MAX_VALUE</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>decoderMaxLineLength</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Set the textline protocol decoder max line length. By default the default value of Mina itself is used which are 1024.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maximumPoolSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>16</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number of worker threads in the worker pool for TCP and UDP (UDP requires <strong>Camel 2.11.3/2.12.2</strong> onwards).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>allowDefaultCodec</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The mina component installs a defaul
 t codec if both, <code>codec</code> is <code>null</code> and <code>textline</code> is <code>false</code>. Setting <code>allowDefaultCodec</code> to <code>false</code> prevents the mina component from installing a default codec as the first element in the filter chain. This is useful in scenarios where another filter must be the first in the filter chain, like the SSL filter.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>disconnectOnNoReply</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If sync is enabled then this option dictates MinaConsumer if it should disconnect where there is no reply to send back.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>noReplyLogLevel</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>WARN</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If sync is enabled this
  option dictates MinaConsumer which logging level to use when logging a there is no reply to send back. Values are: <code>FATAL, ERROR, INFO, DEBUG, OFF</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>orderedThreadPoolExecutor</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether to use ordered thread pool, to ensure events are processed orderly on the same channel.</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>SSL configuration using an <code>org.apache.camel.util.jsse.SSLContextParameters</code> instance. See <a shape="rect" class="unresolved" href="#">Using the JSSE Configuration Utility</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"
 ><p><code>autoStartTls</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether to auto start SSL handshake.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>cachedAddress</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>true</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.14:</strong> Whether to create the InetAddress once and reuse. Setting this to <code>false</code> allows to pickup DNS changes in the network.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>clientMode</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.15:</strong> Consumer only. If the <code>clientMode</code> is true, mina consumer will connect the address as a TCP client.</td></tr></tbody></table></div></div>
 
 
-<h3 id="MINA2-Usingacustomcodec">Using a custom codec</h3><p>See the Mina how to write your own codec. To use your custom codec with <code>camel-mina</code>, you should register your codec in the <a shape="rect" href="registry.html">Registry</a>; for example, by creating a bean in the Spring XML file. Then use the <code>codec</code> option to specify the bean ID of your codec. See <a shape="rect" href="hl7.html">HL7</a> that has a custom codec.</p><h3 id="MINA2-Samplewithsync=false">Sample with sync=false</h3><p>In this sample, Camel exposes a service that listens for TCP connections on port 6200. We use the <strong>textline</strong> codec. In our route, we create a Mina consumer endpoint that listens on port 6200:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="MINA2-Usingacustomcodec">Using a custom codec</h3><p>See the Mina how to write your own codec. To use your custom codec with <code>camel-mina</code>, you should register your codec in the <a shape="rect" href="registry.html">Registry</a>; for example, by creating a bean in the Spring XML file. Then use the <code>codec</code> option to specify the bean ID of your codec. See <a shape="rect" href="hl7.html">HL7</a> that has a custom codec.</p><h3 id="MINA2-Samplewithsync=false">Sample with sync=false</h3><p>In this sample, Camel exposes a service that listens for TCP connections on port 6200. We use the <strong>textline</strong> codec. In our route, we create a Mina consumer endpoint that listens on port 6200:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("mina2:tcp://localhost:" + port1 + "?textline=true&amp;sync=false").to("mock:result");
 </pre>
-</div></div><p>As the sample is part of a unit test, we test it by sending some data to it on port 6200.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>As the sample is part of a unit test, we test it by sending some data to it on port 6200.</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">MockEndpoint mock = getMockEndpoint("mock:result");
 mock.expectedBodiesReceived("Hello World");
  
@@ -115,7 +115,7 @@ template.sendBody("mina2:tcp://localhost
  
 assertMockEndpointsSatisfied();
 </pre>
-</div></div><h3 id="MINA2-Samplewithsync=true">Sample with sync=true</h3><p>In the next sample, we have a more common use case where we expose a TCP service on port 6201 also use the textline codec. However, this time we want to return a response, so we set the <code>sync</code> option to <code>true</code> on the consumer.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="MINA2-Samplewithsync=true">Sample with sync=true</h3><p>In the next sample, we have a more common use case where we expose a TCP service on port 6201 also use the textline codec. However, this time we want to return a response, so we set the <code>sync</code> option to <code>true</code> on the consumer.</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("mina2:tcp://localhost:" + port2 + "?textline=true&amp;sync=true").process(new Processor() {
     public void process(Exchange exchange) throws Exception {
         String body = exchange.getIn().getBody(String.class);
@@ -123,23 +123,23 @@ assertMockEndpointsSatisfied();
     }
 });
 </pre>
-</div></div><p>Then we test the sample by sending some data and retrieving the response using the <code>template.requestBody()</code> method. As we know the response is a <code>String</code>, we cast it to <code>String</code> and can assert that the response is, in fact, something we have dynamically set in our processor code logic.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Then we test the sample by sending some data and retrieving the response using the <code>template.requestBody()</code> method. As we know the response is a <code>String</code>, we cast it to <code>String</code> and can assert that the response is, in fact, something we have dynamically set in our processor code logic.</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">String response = (String)template.requestBody("mina2:tcp://localhost:" + port2 + "?textline=true&amp;sync=true", "World");
 assertEquals("Bye World", response);
 </pre>
-</div></div><h3 id="MINA2-SamplewithSpringDSL">Sample with Spring DSL</h3><p>Spring DSL can, of course, also be used for <a shape="rect" href="mina.html">MINA</a>. In the sample below we expose a TCP server on port 5555:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="MINA2-SamplewithSpringDSL">Sample with Spring DSL</h3><p>Spring DSL can, of course, also be used for <a shape="rect" href="mina.html">MINA</a>. In the sample below we expose a TCP server on port 5555:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">   &lt;route&gt;
      &lt;from uri="mina2:tcp://localhost:5555?textline=true"/&gt;
      &lt;to uri="bean:myTCPOrderHandler"/&gt;
   &lt;/route&gt;
 </pre>
-</div></div><p>In the route above, we expose a TCP server on port 5555 using the textline codec. We let the Spring bean with ID, <code>myTCPOrderHandler</code>, handle the request and return a reply. For instance, the handler bean could be implemented as follows:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>In the route above, we expose a TCP server on port 5555 using the textline codec. We let the Spring bean with ID, <code>myTCPOrderHandler</code>, handle the request and return a reply. For instance, the handler bean could be implemented as follows:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">    public String handleOrder(String payload) {
         ...
         return "Order: OK"
    }
 </pre>
-</div></div><h3 id="MINA2-ClosingSessionWhenComplete">Closing Session When Complete</h3><p>When acting as a server you sometimes want to close the session when, for example, a client conversion is finished. To instruct Camel to close the session, you should add a header with the key <code>CamelMinaCloseSessionWhenComplete</code> set to a boolean <code>true</code> value.</p><p>For instance, the example below will close the session after it has written the <code>bye</code> message back to the client:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="MINA2-ClosingSessionWhenComplete">Closing Session When Complete</h3><p>When acting as a server you sometimes want to close the session when, for example, a client conversion is finished. To instruct Camel to close the session, you should add a header with the key <code>CamelMinaCloseSessionWhenComplete</code> set to a boolean <code>true</code> value.</p><p>For instance, the example below will close the session after it has written the <code>bye</code> message back to the client:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">        from("mina2:tcp://localhost:8080?sync=true&amp;textline=true").process(new Processor() {
             public void process(Exchange exchange) throws Exception {
                 String body = exchange.getIn().getBody(String.class);

Modified: websites/production/camel/content/mvel-component.html
==============================================================================
--- websites/production/camel/content/mvel-component.html (original)
+++ websites/production/camel/content/mvel-component.html Sun Mar 31 15:23:07 2019
@@ -94,7 +94,7 @@
 <p>The <strong>mvel:</strong> component allows you to process a message using an <a shape="rect" class="external-link" href="http://mvel.codehaus.org/" rel="nofollow">MVEL</a> template. This can be ideal when using <a shape="rect" href="templating.html">Templating</a> to generate responses for requests.</p>
 
 <p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
 &lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
@@ -107,7 +107,7 @@
 
 <h3 id="MVELComponent-URIformat">URI format</h3>
 
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
 mvel:templateName[?options]
 </pre>
@@ -160,7 +160,7 @@ mvel:templateName[?options]
 
 <p>For example you could use something like</p>
 
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
 from("activemq:My.Queue").
   to("mvel:com/acme/MyResponse.mvel");
@@ -171,7 +171,7 @@ from("activemq:My.Queue").
 
 <p>To specify what template the component should use dynamically via a header, so for example:</p>
 
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
 from("direct:in").
   setHeader("CamelMvelResourceUri").constant("path/to/my/template.mvel").
@@ -181,7 +181,7 @@ from("direct:in").
 
 <p>To specify a template directly as a header the component should use dynamically via a header, so for example:</p>
 
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
 from("direct:in").
   setHeader("CamelMvelTemplate").constant("@{\"The result is \" + request.body * 3}\" }").

Modified: websites/production/camel/content/mvel.html
==============================================================================
--- websites/production/camel/content/mvel.html (original)
+++ websites/production/camel/content/mvel.html Sun Mar 31 15:23:07 2019
@@ -87,12 +87,12 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Mvel-Mvel">Mvel</h2><p>Camel allows Mvel to be used as an <a shape="rect" href="expression.html">Expression</a> or <a shape="rect" href="predicate.html">Predicate</a> the <a shape="rect" href="dsl.html">DSL</a> or <a shape="rect" href="xml-configuration.html">Xml Configuration</a>.</p><p>You could use Mvel to create an <a shape="rect" href="predicate.html">Predicate</a> in a <a shape="rect" href="message-filter.html">Message Filter</a> or as an <a shape="rect" href="expression.html">Expression</a> for a <a shape="rect" href="recipient-list.html">Recipient List</a></p><p>You can use Mvel dot notation to invoke operations. If you for instance have a body that contains a POJO that has a <code>getFamiliyName</code> method then you can construct the syntax as follows:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="Mvel-Mvel">Mvel</h2><p>Camel allows Mvel to be used as an <a shape="rect" href="expression.html">Expression</a> or <a shape="rect" href="predicate.html">Predicate</a> the <a shape="rect" href="dsl.html">DSL</a> or <a shape="rect" href="xml-configuration.html">Xml Configuration</a>.</p><p>You could use Mvel to create an <a shape="rect" href="predicate.html">Predicate</a> in a <a shape="rect" href="message-filter.html">Message Filter</a> or as an <a shape="rect" href="expression.html">Expression</a> for a <a shape="rect" href="recipient-list.html">Recipient List</a></p><p>You can use Mvel dot notation to invoke operations. If you for instance have a body that contains a POJO that has a <code>getFamiliyName</code> method then you can construct the syntax as follows:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">"request.body.familyName"
    // or 
 "getRequest().getBody().getFamilyName()"
 </pre>
-</div></div><h3 id="Mvel-Variables">Variables</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Variable</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><strong>this</strong></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Exchange</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the Exchange is the root object</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Exchange</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the Exchange object</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>exception</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Throwable</p></td><td colspan="1" rowspan="1" class="confluenceTd
 "><p>the Exchange exception (if any)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>exchangeId</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the exchange id</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>fault</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the Fault message (if any)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the exchange.in message</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the exchange.out message (if any)</p></td></tr><tr><td colspan="1" rowsp
 an="1" class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Map</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the exchange properties</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>property(name)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the property by the given name</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>property(name, type)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Type</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the property by the given name as the given type</p></td></tr></tbody></table></div><h3 id="Mvel-Samples">Samples</h3><p>For example you could use Mvel inside a <a shape="rect" href="message-filter.html">Message Filter</a> in XML</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1
 px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="Mvel-Variables">Variables</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Variable</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><strong>this</strong></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Exchange</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the Exchange is the root object</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Exchange</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the Exchange object</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>exception</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Throwable</p></td><td colspan="1" rowspan="1" class="confluenceTd
 "><p>the Exchange exception (if any)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>exchangeId</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the exchange id</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>fault</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the Fault message (if any)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the exchange.in message</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the exchange.out message (if any)</p></td></tr><tr><td colspan="1" rowsp
 an="1" class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Map</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the exchange properties</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>property(name)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the property by the given name</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>property(name, type)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Type</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the property by the given name as the given type</p></td></tr></tbody></table></div><h3 id="Mvel-Samples">Samples</h3><p>For example you could use Mvel inside a <a shape="rect" href="message-filter.html">Message Filter</a> in XML</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="c
 ode"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;route&gt;
   &lt;from uri="seda:foo"/&gt;
   &lt;filter&gt;
@@ -101,13 +101,13 @@
   &lt;/filter&gt;
 &lt;/route&gt;
 </pre>
-</div></div><p>And the sample using Java DSL:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>And the sample using Java DSL:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">   from("seda:foo").filter().mvel("request.headers.foo == 'bar'").to("seda:bar");
 </pre>
-</div></div><h3 id="Mvel-Loadingscriptfromexternalresource">Loading script from external resource</h3><p><strong>Available as of Camel 2.11</strong></p><p>You can externalize the script and have Camel load it from a resource such as <code>"classpath:"</code>, <code>"file:"</code>, or <code>"http:"</code>.<br clear="none"> This is done using the following syntax: <code>"resource:scheme:location"</code>, eg to refer to a file on the classpath you can do:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="Mvel-Loadingscriptfromexternalresource">Loading script from external resource</h3><p><strong>Available as of Camel 2.11</strong></p><p>You can externalize the script and have Camel load it from a resource such as <code>"classpath:"</code>, <code>"file:"</code>, or <code>"http:"</code>.<br clear="none"> This is done using the following syntax: <code>"resource:scheme:location"</code>, eg to refer to a file on the classpath you can do:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">.setHeader("myHeader").mvel("resource:classpath:script.mvel")
 </pre>
-</div></div><h3 id="Mvel-Dependencies">Dependencies</h3><p>To use Mvel in your camel routes you need to add the a dependency on <strong>camel-mvel</strong> which implements the Mvel language.</p><p>If you use maven you could just add the following to your pom.xml, substituting the version number for the latest &amp; greatest release (see <a shape="rect" href="download.html">the download page for the latest versions</a>).</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="Mvel-Dependencies">Dependencies</h3><p>To use Mvel in your camel routes you need to add the a dependency on <strong>camel-mvel</strong> which implements the Mvel language.</p><p>If you use maven you could just add the following to your pom.xml, substituting the version number for the latest &amp; greatest release (see <a shape="rect" href="download.html">the download page for the latest versions</a>).</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;dependency&gt;
   &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
   &lt;artifactId&gt;camel-mvel&lt;/artifactId&gt;

Modified: websites/production/camel/content/netty-http.html
==============================================================================
--- websites/production/camel/content/netty-http.html (original)
+++ websites/production/camel/content/netty-http.html Sun Mar 31 15:23:07 2019
@@ -88,7 +88,7 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="NettyHTTP-NettyHTTPComponent">Netty HTTP Component</h2><p><strong>Available as of Camel 2.12</strong></p><p>The <strong>netty-http</strong> component is an extension to <a shape="rect" href="netty.html">Netty</a> component to facilitiate HTTP transport with <a shape="rect" href="netty.html">Netty</a>.</p><p>This camel component supports both producer and consumer endpoints.</p><div class="confluence-information-macro confluence-information-macro-warning conf-macro output-block" data-hasbody="true" data-macro-name="warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>This component is deprecated. You should use <a shape="rect" href="netty4-http.html">Netty4 HTTP</a>.</p></div></div><div class="confluence-information-macro confluence-information-macro-information conf-macro output-block" data-hasbody="true" data-macro-name="info"><p cla
 ss="title">Stream</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>Netty is stream based, which means the input it receives is submitted to Camel as a stream. That means you will only be able to read the content of the stream <strong>once</strong>.<br clear="none"> If you find a situation where the message body appears to be empty or you need to access the data multiple times (eg: doing multicasting, or redelivery error handling)<br clear="none"> you should use <a shape="rect" href="stream-caching.html">Stream caching</a> or convert the message body to a <code>String</code> which is safe to be re-read multiple times.</p><p><span>Notice Netty4 HTTP reads the entire stream into memory using </span><code>io.netty.handler.codec.http.HttpObjectAggregator</code><span> to build the entire full http message. But the resulting message is still a stream based message which is readable once.</
 span></p></div></div><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="NettyHTTP-NettyHTTPComponent">Netty HTTP Component</h2><p><strong>Available as of Camel 2.12</strong></p><p>The <strong>netty-http</strong> component is an extension to <a shape="rect" href="netty.html">Netty</a> component to facilitiate HTTP transport with <a shape="rect" href="netty.html">Netty</a>.</p><p>This camel component supports both producer and consumer endpoints.</p><div class="confluence-information-macro confluence-information-macro-warning conf-macro output-block" data-hasbody="true" data-macro-name="warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>This component is deprecated. You should use <a shape="rect" href="netty4-http.html">Netty4 HTTP</a>.</p></div></div><div class="confluence-information-macro confluence-information-macro-information conf-macro output-block" data-hasbody="true" data-macro-name="info"><p cla
 ss="title">Stream</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>Netty is stream based, which means the input it receives is submitted to Camel as a stream. That means you will only be able to read the content of the stream <strong>once</strong>.<br clear="none"> If you find a situation where the message body appears to be empty or you need to access the data multiple times (eg: doing multicasting, or redelivery error handling)<br clear="none"> you should use <a shape="rect" href="stream-caching.html">Stream caching</a> or convert the message body to a <code>String</code> which is safe to be re-read multiple times.</p><p><span>Notice Netty4 HTTP reads the entire stream into memory using </span><code>io.netty.handler.codec.http.HttpObjectAggregator</code><span> to build the entire full http message. But the resulting message is still a stream based message which is readable once.</
 span></p></div></div><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-netty-http&lt;/artifactId&gt;
@@ -96,7 +96,7 @@
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 </pre>
-</div></div><h3 id="NettyHTTP-URIformat">URI format</h3><p>The URI scheme for a netty component is as follows</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="NettyHTTP-URIformat">URI format</h3><p>The URI scheme for a netty component is as follows</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">netty-http:http://localhost:8080[?options]
 </pre>
 </div></div><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p><div class="confluence-information-macro confluence-information-macro-information conf-macro output-block" data-hasbody="true" data-macro-name="info"><p class="title">Query parameters vs endpoint options</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>You may be wondering how Camel recognizes URI query parameters and endpoint options. For example you might create endpoint URI as follows - <code>netty-http:http//example.com?myParam=myValue&amp;compression=true</code> . In this example <code>myParam</code> is the HTTP parameter, while <code>compression</code> is the Camel endpoint option. The strategy used by Camel in such situations is to resolve available endpoint options and remove them from the URI. It means that for the discussed example, the HTT
 P request sent by Netty HTTP producer to the endpoint will look as follows -&#160;<code>http//example.com?myParam=myValue</code> , because <code>compression</code> endpoint option will be resolved and removed from the target URL.</p><p>Keep also in mind that you cannot specify endpoint options using dynamic headers (like <code>CamelHttpQuery</code>). Endpoint options can be specified only at the endpoint URI definition level (like <code>to</code> or <code>from</code> DSL elements).</p></div></div><h3 id="NettyHTTP-HTTPOptions">HTTP Options</h3><div class="confluence-information-macro confluence-information-macro-information conf-macro output-block" data-hasbody="true" data-macro-name="info"><p class="title">A lot more options</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p><strong>Important:</strong> This component inherits all the options from <a shape="rect" href="netty.html">Net
 ty</a>. So make sure to look at the <a shape="rect" href="netty.html">Netty</a> documentation as well.<br clear="none"> Notice that some options from <a shape="rect" href="netty.html">Netty</a> is not applicable when using this <a shape="rect" href="netty-http.html">Netty HTTP</a> component, such as options related to UDP transport.</p></div></div><div class="confluenceTableSmall conf-macro output-block" data-hasbody="true" data-macro-name="div"><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>chunkedMaxContentLength</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1mb</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Value in bytes the max content leng
 th per chunked frame received on the Netty HTTP server.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>compression</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allow using gzip/deflate for compression on the Netty HTTP server if the client supports it from the HTTP headers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>headerFilterStrategy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To use a custom <code>org.apache.camel.spi.HeaderFilterStrategy</code> to filter headers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>httpMethodRestrict</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To disable HTTP methods on the Netty HTTP con
 sumer. You can specify multiple separated by comma.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>mapHeaders</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If this option is enabled, then during binding from Netty to Camel <a shape="rect" href="message.html">Message</a> then the headers will be mapped as well (eg added as header to the Camel <a shape="rect" href="message.html">Message</a> as well). You can turn off this option to disable this. The headers can still be accessed from the <code>org.apache.camel.component.netty.http.NettyHttpMessage</code> message with the method <code>getHttpRequest()</code> that returns the Netty HTTP request <code>org.jboss.netty.handler.codec.http.HttpRequest</code> instance.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>matchOnUriPrefix</code></p></td><td colspan="1" rowspan="1" class="confluenc
 eTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether or not Camel should try to find a target consumer by matching the URI prefix if no exact match is found. See further below for more details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>nettyHttpBinding</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To use a custom <code>org.apache.camel.component.netty.http.NettyHttpBinding</code> for binding to/from Netty and Camel Message API.</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 <code>true</code>, the producer will ignore the <code>Exchange.HTTP_URI</code> header, and use the endpoint's URI for request. You may also set the <
 code>throwExceptionOnFailure</code> to be <code>false</code> to let the producer send all the fault response back. The consumer working in the bridge mode will skip the gzip compression and WWW URL form encoding (by adding the <code>Exchange.SKIP_GZIP_ENCODING</code> and <code>Exchange.SKIP_WWW_FORM_URLENCODED</code> headers to the consumed exchange).</p></td></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>HttpOperationFailedException</code> in case of failed responses from the remote server. This allows you to get all responses regardles of the HTTP status code.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>traceEnabled</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rows
 pan="1" class="confluenceTd"><p>Specifies whether to enable HTTP TRACE for this Netty HTTP consumer. By default TRACE is turned off.</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 Exception was send back serialized in the response as a <code>application/x-java-serialized-object</code> content type. On the producer side the exception will be deserialized and thrown as is, instead of the <code>HttpOperationFailedException</code>. The caused exception is required to be serialized.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>urlDecodeHeaders</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspa
 n="1" class="confluenceTd"><p>If this option is enabled, then during binding from Netty to Camel <a shape="rect" href="message.html">Message</a> then the header values will be URL decoded (eg %20 will be a space character. Notice this option is used by the default <code>org.apache.camel.component.netty.http.NettyHttpBinding</code> and therefore if you implement a custom <code>org.apache.camel.component.netty.http.NettyHttpBinding</code> then you would need to decode the headers accordingly to this option. <strong>Notice:</strong> This option is default <code>true</code> for Camel 2.12.x, and default <code>false</code> from Camel 2.13 onwards.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>nettySharedHttpServer</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 shared <a shape="rect" href="netty-http.html">Netty HTTP</a> server. See <a shape="rect" href="
 netty-http-server-example.html">Netty HTTP Server Example</a> for more details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>disableStreamCache</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Determines whether or not the raw input stream from Netty <code>HttpRequest#getContent()</code> is cached or not (Camel will read the stream into a in light-weight memory based Stream caching) cache. By default Camel will cache the Netty input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to <code>true</code> when you for example need to access the raw stream, such as streaming it directly to a file or other persistent store. Mind that if you enable this option, then you cannot read the Netty stream multiple times out of the box, and you would need manually to reset the reader index
  on the Netty raw stream.</p><p><span>Notice Netty4 HTTP reads the entire stream into memory using </span><code>io.netty.handler.codec.http.HttpObjectAggregator</code><span> to build the entire full http message. But the resulting message is still a stream based message which is readable once.</span></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>securityConfiguration</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>Consumer only</strong>. Refers to a <code>org.apache.camel.component.netty.http.NettyHttpSecurityConfiguration</code> for configuring secure web resources.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>send503whenSuspended</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Consumer only</strong>. Whether to send 
 back HTTP status code 503 when the consumer has been suspended. If the option is <code>false</code> then the Netty Acceptor is unbound when the consumer is suspended, so clients cannot connect anymore.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>maxHeaderSize</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>8192</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.15.3:</strong>&#160;<strong>Consumer only. </strong>The maximum length of all headers. If the sum of the length of each header exceeds this value, a TooLongFrameException will be raised.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>okStatusCodeRange</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>200-299</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.16:</strong><span> The status codes which is considered a success response. The values are inclusive. The range must be defined as from-to 
 with the dash included.</span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><span class="hl_identifier">useRelativePath</span></td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.16: Producer only:</strong> Whether to use a path (/myapp) in the request line or an absolute URI (<a shape="rect" class="external-link" href="http://0.0.0.0:8080/myapp%29," rel="nofollow">http://0.0.0.0:8080/myapp),</a> which is default.</td></tr></tbody></table></div></div>
@@ -108,34 +108,34 @@
 <h3 id="NettyHTTP-MessageHeaders">Message Headers</h3><p>The following headers can be used on the producer to control the HTTP request.</p><div class="confluenceTableSmall conf-macro output-block" data-hasbody="true" data-macro-name="div"><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>CamelHttpMethod</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allow to control what HTTP method to use such as GET, POST, TRACE etc. The type can also be a <code>org.jboss.netty.handler.codec.http.HttpMethod</code> instance.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelHttpQuery</code><
 /p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allows to provide URI query parameters as a <code>String</code> value that overrides the endpoint configuration. Separate multiple parameters using the &amp; sign. For example: <code>foo=bar&amp;beer=yes</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelHttpPath</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.13.1/2.12.4:</strong> Allows to provide URI context-path and query parameters as a <code>String</code> value that overrides the endpoint configuration. This allows to reuse the same producer for calling same remote http server, but using a dynamic context-path and query parameters.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Content-Type</code></p></td><td col
 span="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To set the content-type of the HTTP body. For example: <code>text/plain; charset="UTF-8"</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>CamelHttpResponseCode</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>int</code></td><td colspan="1" rowspan="1" class="confluenceTd">Allows to set the HTTP Status code to use. By default 200 is used for success, and 500 for failure.</td></tr></tbody></table></div></div>
 
 
-<p>The following headers is provided as meta-data when a route starts from an <a shape="rect" href="netty-http.html">Netty HTTP</a> endpoint:</p><p>The description in the table takes offset in a route having: <code>from("netty-http:http:0.0.0.0:8080/myapp")...</code></p><div class="confluenceTableSmall conf-macro output-block" data-hasbody="true" data-macro-name="div"><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>CamelHttpMethod</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 method used, such as GET, POST, TRACE etc.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>C
 amelHttpUrl</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 URL including protocol, host and port, etc:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<p>The following headers is provided as meta-data when a route starts from an <a shape="rect" href="netty-http.html">Netty HTTP</a> endpoint:</p><p>The description in the table takes offset in a route having: <code>from("netty-http:http:0.0.0.0:8080/myapp")...</code></p><div class="confluenceTableSmall conf-macro output-block" data-hasbody="true" data-macro-name="div"><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>CamelHttpMethod</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 method used, such as GET, POST, TRACE etc.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>C
 amelHttpUrl</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 URL including protocol, host and port, etc:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">http://0.0.0.0:8080/myapp</pre>
-</div></div></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelHttpUri</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 URI without protocol, host and port, etc:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelHttpUri</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 URI without protocol, host and port, etc:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">/myapp</pre>
 </div></div></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelHttpQuery</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Any query parameters, such as <code>foo=bar&amp;beer=yes</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelHttpRawQuery</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.13.0</strong>: Any query parameters, such as <code>foo=bar&amp;beer=yes</code>. Stored in the raw form, as they arrived to the consumer (i.e. before URL decoding).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelHttpPath</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Additional context-path. This v
 alue is empty if the client called the context-path <code>/myapp</code>. If the client calls <code>/myapp/mystuff</code>, then this header value is <code>/mystuff</code>. In other words its the value after the context-path configured on the route endpoint.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelHttpCharacterEncoding</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 charset from the content-type header.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelHttpAuthentication</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If the user was authenticated using HTTP Basic then this header is added with the value <code>Basic</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>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 content type if provided. For example: <code>text/plain; charset="UTF-8"</code>.</p></td></tr></tbody></table></div></div>
 
 
-<h3 id="NettyHTTP-AccesstoNettytypes">Access to Netty types</h3><p>This component uses the <code>org.apache.camel.component.netty.http.NettyHttpMessage</code> as the message implementation on the <a shape="rect" href="exchange.html">Exchange</a>. This allows end users to get access to the original Netty request/response instances if needed, as shown below. Mind that the original response may not be accessible at all times.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="NettyHTTP-AccesstoNettytypes">Access to Netty types</h3><p>This component uses the <code>org.apache.camel.component.netty.http.NettyHttpMessage</code> as the message implementation on the <a shape="rect" href="exchange.html">Exchange</a>. This allows end users to get access to the original Netty request/response instances if needed, as shown below. Mind that the original response may not be accessible at all times.</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">org.jboss.netty.handler.codec.http.HttpRequest request = exchange.getIn(NettyHttpMessage.class).getHttpRequest();
 </pre>
-</div></div><h3 id="NettyHTTP-Examples">Examples</h3><p>In the route below we use <a shape="rect" href="netty-http.html">Netty HTTP</a> as a HTTP server, which returns back a hardcoded "Bye World" message.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="NettyHTTP-Examples">Examples</h3><p>In the route below we use <a shape="rect" href="netty-http.html">Netty HTTP</a> as a HTTP server, which returns back a hardcoded "Bye World" message.</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">    from("netty-http:http://0.0.0.0:8080/foo")
       .transform().constant("Bye World");
 </pre>
-</div></div><p>And we can call this HTTP server using Camel also, with the <a shape="rect" href="producertemplate.html">ProducerTemplate</a> as shown below:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>And we can call this HTTP server using Camel also, with the <a shape="rect" href="producertemplate.html">ProducerTemplate</a> as shown below:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">    String out = template.requestBody("netty-http:http://localhost:8080/foo", "Hello World", String.class);
     System.out.println(out);
 </pre>
-</div></div><p>And we get back "Bye World" as the output.</p><h3 id="NettyHTTP-HowdoIletNettymatchwildcards">How do I let Netty match wildcards</h3><p>By default <a shape="rect" href="netty-http.html">Netty HTTP</a> will only match on exact uri's. But you can instruct Netty to match prefixes. For example</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>And we get back "Bye World" as the output.</p><h3 id="NettyHTTP-HowdoIletNettymatchwildcards">How do I let Netty match wildcards</h3><p>By default <a shape="rect" href="netty-http.html">Netty HTTP</a> will only match on exact uri's. But you can instruct Netty to match prefixes. For example</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("netty-http:http://0.0.0.0:8123/foo").to("mock:foo");
 </pre>
-</div></div><p>In the route above <a shape="rect" href="netty-http.html">Netty HTTP</a> will only match if the uri is an exact match, so it will match if you enter<br clear="none"> <code><a shape="rect" class="external-link" href="http://0.0.0.0:8123/foo" rel="nofollow">http://0.0.0.0:8123/foo</a></code> but not match if you do <code><a shape="rect" class="external-link" href="http://0.0.0.0:8123/foo/bar" rel="nofollow">http://0.0.0.0:8123/foo/bar</a></code>.</p><p>So if you want to enable wildcard matching you do as follows:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>In the route above <a shape="rect" href="netty-http.html">Netty HTTP</a> will only match if the uri is an exact match, so it will match if you enter<br clear="none"> <code><a shape="rect" class="external-link" href="http://0.0.0.0:8123/foo" rel="nofollow">http://0.0.0.0:8123/foo</a></code> but not match if you do <code><a shape="rect" class="external-link" href="http://0.0.0.0:8123/foo/bar" rel="nofollow">http://0.0.0.0:8123/foo/bar</a></code>.</p><p>So if you want to enable wildcard matching you do as follows:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("netty-http:http://0.0.0.0:8123/foo?matchOnUriPrefix=true").to("mock:foo");
 </pre>
-</div></div><p>So now Netty matches any endpoints with starts with <code>foo</code>.</p><p>To match <strong>any</strong> endpoint you can do:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>So now Netty matches any endpoints with starts with <code>foo</code>.</p><p>To match <strong>any</strong> endpoint you can do:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("netty-http:http://0.0.0.0:8123?matchOnUriPrefix=true").to("mock:foo");
 </pre>
-</div></div><h3 id="NettyHTTP-Usingmultiplerouteswithsameport">Using multiple routes with same port</h3><p>In the same <a shape="rect" href="camelcontext.html">CamelContext</a> you can have multiple routes from <a shape="rect" href="netty-http.html">Netty HTTP</a> that shares the same port (eg a <code>org.jboss.netty.bootstrap.ServerBootstrap</code> instance). Doing this requires a number of bootstrap options to be identical in the routes, as the routes will share the same <code>org.jboss.netty.bootstrap.ServerBootstrap</code> instance. The instance will be configured with the options from the first route created.</p><p>The options the routes must be identical configured is all the options defined in the <code>org.apache.camel.component.netty.NettyServerBootstrapConfiguration</code> configuration class. If you have configured another route with different options, Camel will throw an exception on startup, indicating the options is not identical. To mitigate this ensure all options is
  identical.</p><p>Here is an example with two routes that share the same port.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Two routes sharing the same port</b></div><div class="codeContent panelContent pdl">
+</div></div><h3 id="NettyHTTP-Usingmultiplerouteswithsameport">Using multiple routes with same port</h3><p>In the same <a shape="rect" href="camelcontext.html">CamelContext</a> you can have multiple routes from <a shape="rect" href="netty-http.html">Netty HTTP</a> that shares the same port (eg a <code>org.jboss.netty.bootstrap.ServerBootstrap</code> instance). Doing this requires a number of bootstrap options to be identical in the routes, as the routes will share the same <code>org.jboss.netty.bootstrap.ServerBootstrap</code> instance. The instance will be configured with the options from the first route created.</p><p>The options the routes must be identical configured is all the options defined in the <code>org.apache.camel.component.netty.NettyServerBootstrapConfiguration</code> configuration class. If you have configured another route with different options, Camel will throw an exception on startup, indicating the options is not identical. To mitigate this ensure all options is
  identical.</p><p>Here is an example with two routes that share the same port.</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Two routes sharing the same port</b></div><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("netty-http:http://0.0.0.0:{{port}}/foo")
   .to("mock:foo")
   .transform().constant("Bye World");
@@ -144,7 +144,7 @@ from("netty-http:http://0.0.0.0:{{port}}
   .to("mock:bar")
   .transform().constant("Bye Camel");
 </pre>
-</div></div><p>And here is an example of a mis configured 2nd route that do not have identical <code>org.apache.camel.component.netty.NettyServerBootstrapConfiguration</code> option as the 1st route. This will cause Camel to fail on startup.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Two routes sharing the same port, but the 2nd route is misconfigured and will fail on starting</b></div><div class="codeContent panelContent pdl">
+</div></div><p>And here is an example of a mis configured 2nd route that do not have identical <code>org.apache.camel.component.netty.NettyServerBootstrapConfiguration</code> option as the 1st route. This will cause Camel to fail on startup.</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Two routes sharing the same port, but the 2nd route is misconfigured and will fail on starting</b></div><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("netty-http:http://0.0.0.0:{{port}}/foo")
   .to("mock:foo")
   .transform().constant("Bye World");
@@ -154,14 +154,14 @@ from("netty-http:http://0.0.0.0:{{port}}
   .to("mock:bar")
   .transform().constant("Bye Camel");
 </pre>
-</div></div><h4 id="NettyHTTP-Reusingsameserverbootstrapconfigurationwithmultipleroutes">Reusing same server bootstrap configuration with multiple routes</h4><p>By configuring the common server bootstrap option in an single instance of a <code>org.apache.camel.component.netty.NettyServerBootstrapConfiguration</code> type, we can use the <code>bootstrapConfiguration</code> option on the <a shape="rect" href="netty-http.html">Netty HTTP</a> consumers to refer and reuse the same options across all consumers.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="NettyHTTP-Reusingsameserverbootstrapconfigurationwithmultipleroutes">Reusing same server bootstrap configuration with multiple routes</h4><p>By configuring the common server bootstrap option in an single instance of a <code>org.apache.camel.component.netty.NettyServerBootstrapConfiguration</code> type, we can use the <code>bootstrapConfiguration</code> option on the <a shape="rect" href="netty-http.html">Netty HTTP</a> consumers to refer and reuse the same options across all consumers.</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;bean id="nettyHttpBootstrapOptions" class="org.apache.camel.component.netty.NettyServerBootstrapConfiguration"&gt;
   &lt;property name="backlog" value="200"/&gt;
   &lt;property name="connectTimeout" value="20000"/&gt;
   &lt;property name="workerCount" value="16"/&gt;
 &lt;/bean&gt;
 </pre>
-</div></div><p>And in the routes you refer to this option as shown below</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>And in the routes you refer to this option as shown below</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;route&gt;
   &lt;from uri="netty-http:http://0.0.0.0:{{port}}/foo?bootstrapConfiguration=#nettyHttpBootstrapOptions"/&gt;
   ...
@@ -177,13 +177,13 @@ from("netty-http:http://0.0.0.0:{{port}}
   ...
 &lt;/route&gt;
 </pre>
-</div></div><h4 id="NettyHTTP-ReusingsameserverbootstrapconfigurationwithmultipleroutesacrossmultiplebundlesinOSGicontainer">Reusing same server bootstrap configuration with multiple routes across multiple bundles in OSGi container</h4><p>See the <a shape="rect" href="netty-http-server-example.html">Netty HTTP Server Example</a> for more details and example how to do that.</p><h3 id="NettyHTTP-UsingHTTPBasicAuthentication">Using HTTP Basic Authentication</h3><p>The <a shape="rect" href="netty-http.html">Netty HTTP</a> consumer supports HTTP basic authentication by specifying the security realm name to use, as shown below</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="NettyHTTP-ReusingsameserverbootstrapconfigurationwithmultipleroutesacrossmultiplebundlesinOSGicontainer">Reusing same server bootstrap configuration with multiple routes across multiple bundles in OSGi container</h4><p>See the <a shape="rect" href="netty-http-server-example.html">Netty HTTP Server Example</a> for more details and example how to do that.</p><h3 id="NettyHTTP-UsingHTTPBasicAuthentication">Using HTTP Basic Authentication</h3><p>The <a shape="rect" href="netty-http.html">Netty HTTP</a> consumer supports HTTP basic authentication by specifying the security realm name to use, as shown below</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;route&gt;
    &lt;from uri="netty-http:http://0.0.0.0:{{port}}/foo?securityConfiguration.realm=karaf"/&gt;
    ...
 &lt;/route&gt;
 </pre>
-</div></div><p>The realm name is mandatory to enable basic authentication. By default the JAAS based authenticator is used, which will use the realm name specified (karaf in the example above) and use the JAAS realm and the JAAS {{LoginModule}}s of this realm for authentication.</p><p>End user of Apache Karaf / ServiceMix has a karaf realm out of the box, and hence why the example above would work out of the box in these containers.</p><h4 id="NettyHTTP-SpecifyingACLonwebresources">Specifying ACL on web resources</h4><p>The <code>org.apache.camel.component.netty.http.SecurityConstraint</code> allows to define constrains on web resources. And the <code>org.apache.camel.component.netty.http.SecurityConstraintMapping</code> is provided out of the box, allowing to easily define inclusions and exclusions with roles.</p><p>For example as shown below in the XML DSL, we define the constraint bean:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="co
 de" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>The realm name is mandatory to enable basic authentication. By default the JAAS based authenticator is used, which will use the realm name specified (karaf in the example above) and use the JAAS realm and the JAAS {{LoginModule}}s of this realm for authentication.</p><p>End user of Apache Karaf / ServiceMix has a karaf realm out of the box, and hence why the example above would work out of the box in these containers.</p><h4 id="NettyHTTP-SpecifyingACLonwebresources">Specifying ACL on web resources</h4><p>The <code>org.apache.camel.component.netty.http.SecurityConstraint</code> allows to define constrains on web resources. And the <code>org.apache.camel.component.netty.http.SecurityConstraintMapping</code> is provided out of the box, allowing to easily define inclusions and exclusions with roles.</p><p>For example as shown below in the XML DSL, we define the constraint bean:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody
 ="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">  &lt;bean id="constraint" class="org.apache.camel.component.netty.http.SecurityConstraintMapping"&gt;
     &lt;!-- inclusions defines url -&gt; roles restrictions --&gt;
     &lt;!-- a * should be used for any role accepted (or even no roles) --&gt;
@@ -202,7 +202,7 @@ from("netty-http:http://0.0.0.0:{{port}}
     &lt;/property&gt;
   &lt;/bean&gt;
 </pre>
-</div></div><p>The constraint above is define so that</p><ul class="alternate"><li>access to /* is restricted and any roles is accepted (also if user has no roles)</li><li>access to /admin/* requires the admin role</li><li>access to /guest/* requires the admin or guest role</li><li>access to /public/* is an exclusion which means no authentication is needed, and is therefore public for everyone without logging in</li></ul><p>To use this constraint we just need to refer to the bean id as shown below:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>The constraint above is define so that</p><ul class="alternate"><li>access to /* is restricted and any roles is accepted (also if user has no roles)</li><li>access to /admin/* requires the admin role</li><li>access to /guest/* requires the admin or guest role</li><li>access to /public/* is an exclusion which means no authentication is needed, and is therefore public for everyone without logging in</li></ul><p>To use this constraint we just need to refer to the bean id as shown below:</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
 <pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;route&gt;
    &lt;from uri="netty-http:http://0.0.0.0:{{port}}/foo?matchOnUriPrefix=true&amp;amp;securityConfiguration.realm=karaf&amp;amp;securityConfiguration.securityConstraint=#constraint"/&gt;
    ...