svn commit: r890002 - in /websites/production/camel/content: cache/main.pageCache camel-2130-release.html netty-http.html

[bu...@apache.org]

Author: buildbot
Date: Wed Dec 11 16:19:16 2013
New Revision: 890002

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-2130-release.html
    websites/production/camel/content/netty-http.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/camel-2130-release.html
==============================================================================
--- websites/production/camel/content/camel-2130-release.html (original)
+++ websites/production/camel/content/camel-2130-release.html Wed Dec 11 16:19:16 2013
@@ -153,7 +153,7 @@
 
 
 <h2><a shape="rect" name="Camel2.13.0Release-Changesthatmayaffectendusers"></a>Changes that may affect end users</h2>
-<ul><li>Components depending on Servlet API has been upgrade from Servlet API 2.5 to 3.0</li><li>Jetty upgraded from 7.6.x to 8.1.x</li><li><a shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a> uses <tt>Object</tt> instead of <tt>String</tt> as the key.</li><li><a shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a> atomic number producer was using incorrect name (<a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-6833">CAMEL-6833</a>).  Name will be different with this release.</li><li><a shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a> instance consumer was incorrectly writing headers to the "out" message as opposed to the "in" message.  Headers are now written to the "in" message.</li><li><a shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a> map/multimap consumer
  were sending header value "envict" when an item was evicted.  This has been corrected and the value "evicted" is used now.</li><li>The enum value <tt>NON_BLOCKING</tt> has been removed in <tt>camel-apns</tt> as its no longer support in APNS itself.</li><li><tt>DefaultTimeoutMap</tt> must call <tt>start</tt> to initialize the map before use.</li><li><tt>@ExcludeRoutes</tt> test annotation now accepts only classes implementing <tt>RoutesBuilder</tt> interface.</li><li>The MBean names registered by <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> no longer include the hostname in the <tt>context</tt> part, eg before <tt>context=myHost/myCamelId</tt> and now after <tt>context=myCamelId</tt>. Having the hostname in the MBean name does not bring much value, and in fact makes things more complicated as the mbean name changes depending on the host running Camel. There is an option <tt>includeHostName</tt> that can be configure as <tt>true</tt> to preserve the old behav
 ior.</li><li><a shape="rect" href="camel-jmx.html" title="Camel JMX">MBean naming</a> in OSGi cleaned up to use simpler naming with symbolicName. Before we could have MBean names with duplicate bundle ids such as <tt>context=114-114-camel-6</tt>, which now is using the symbolic name instead, <tt>context=MyApplication</tt>.</li><li>Added <tt>beforeAddRoutes</tt> and <tt>afterAddRoutes</tt> to <tt>org.apache.camel.component.servletlistener.CamelContextLifecycle</tt> in <a shape="rect" href="servletlistener-component.html" title="ServletListener Component">ServletListener Component</a></li><li>The <a shape="rect" href="language.html" title="Language">Language</a> component now no longer caches the compiled script as that could cause side-effects. You can set <tt>cacheScript=true</tt> to enable the previous behavior if your script is safe to do so.</li></ul>
+<ul><li>Components depending on Servlet API has been upgrade from Servlet API 2.5 to 3.0</li><li>Jetty upgraded from 7.6.x to 8.1.x</li><li><a shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a> uses <tt>Object</tt> instead of <tt>String</tt> as the key.</li><li><a shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a> atomic number producer was using incorrect name (<a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-6833">CAMEL-6833</a>).  Name will be different with this release.</li><li><a shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a> instance consumer was incorrectly writing headers to the "out" message as opposed to the "in" message.  Headers are now written to the "in" message.</li><li><a shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a> map/multimap consumer
  were sending header value "envict" when an item was evicted.  This has been corrected and the value "evicted" is used now.</li><li>The enum value <tt>NON_BLOCKING</tt> has been removed in <tt>camel-apns</tt> as its no longer support in APNS itself.</li><li><tt>DefaultTimeoutMap</tt> must call <tt>start</tt> to initialize the map before use.</li><li><tt>@ExcludeRoutes</tt> test annotation now accepts only classes implementing <tt>RoutesBuilder</tt> interface.</li><li>The MBean names registered by <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> no longer include the hostname in the <tt>context</tt> part, eg before <tt>context=myHost/myCamelId</tt> and now after <tt>context=myCamelId</tt>. Having the hostname in the MBean name does not bring much value, and in fact makes things more complicated as the mbean name changes depending on the host running Camel. There is an option <tt>includeHostName</tt> that can be configure as <tt>true</tt> to preserve the old behav
 ior.</li><li><a shape="rect" href="camel-jmx.html" title="Camel JMX">MBean naming</a> in OSGi cleaned up to use simpler naming with symbolicName. Before we could have MBean names with duplicate bundle ids such as <tt>context=114-114-camel-6</tt>, which now is using the symbolic name instead, <tt>context=MyApplication</tt>.</li><li>Added <tt>beforeAddRoutes</tt> and <tt>afterAddRoutes</tt> to <tt>org.apache.camel.component.servletlistener.CamelContextLifecycle</tt> in <a shape="rect" href="servletlistener-component.html" title="ServletListener Component">ServletListener Component</a></li><li>The <a shape="rect" href="language.html" title="Language">Language</a> component now no longer caches the compiled script as that could cause side-effects. You can set <tt>cacheScript=true</tt> to enable the previous behavior if your script is safe to do so.</li><li>The default value of <tt>urlDecodeHeaders</tt> option on <a shape="rect" href="netty-http.html" title="Netty HTTP">Netty HTTP</a> ha
 s been changed from <tt>true</tt> to <tt>false</tt>.</li></ul>
 
 
 

Modified: websites/production/camel/content/netty-http.html
==============================================================================
--- websites/production/camel/content/netty-http.html (original)
+++ websites/production/camel/content/netty-http.html Wed Dec 11 16:19:16 2013
@@ -128,7 +128,7 @@ netty-http:http://localhost:8080[?option
 Notice that some options from <a shape="rect" href="netty.html" title="Netty">Netty</a> is not applicable when using this <a shape="rect" href="netty-http.html" title="Netty HTTP">Netty HTTP</a> component, such as options related to UDP transport.</td></tr></table></div>
 
 <div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Name </th><th colspan="1" rowspan="1" class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>chunkedMaxContentLength</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1mb</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Value in bytes the max content length per chunked frame received on the Netty HTTP server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>compression</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Allow using gzip/deflate for compression on the Netty HTTP server if the client supports it from the HTTP headers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>headerFilterStrategy</tt> </td><td colspan="1" rowspan="1" c
 lass="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> To use a custom  <tt>org.apache.camel.spi.HeaderFilterStrategy</tt> to filter headers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpMethodRestrict</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> To disable HTTP methods on the Netty HTTP consumer. You can specify multiple separated by comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>mapHeaders</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If this option is enabled, then during binding from Netty to Camel <a shape="rect" href="message.html" title="Message">Message</a> then the headers will be mapped as well (eg added as header to the Camel <a shape="rect" href="message.html" title="Message">Message</a> as well). You can turn off this option to disable
  this. The headers can still be accessed from the <tt>org.apache.camel.component.netty.http.NettyHttpMessage</tt> message with the method <tt>getHttpRequest()</tt> that returns the Netty HTTP request <tt>org.jboss.netty.handler.codec.http.HttpRequest</tt> instance. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>matchOnUriPrefix</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 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. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>nettyHttpBinding</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> To use a custom <tt>org.apache.camel.component.netty.http.NettyHttpBinding</tt> for binding to/from Netty and Camel Message API. </td></tr><tr><td colspan="1" row
 span="1" class="confluenceTd"> <tt>bridgeEndpoint</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If the option is <tt>true</tt>, the producer will ignore the <tt>Exchange.HTTP_URI</tt> header, and use the endpoint's URI for request. You may also set the <tt>throwExceptionOnFailure</tt> to be <tt>false</tt> to let the producer send all the fault response back. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>throwExceptionOnFailure</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to disable throwing the <tt>HttpOperationFailedException</tt> in case of failed responses from the remote server. This allows you to get all responses regardles of the HTTP status code. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>traceEnabled</tt> </td><td colspan="1" rowspan="1" class="confluenceTd
 "> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to enable HTTP TRACE for this Netty HTTP consumer. By default TRACE is turned off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>transferException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If enabled and an <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a <tt>application/x-java-serialized-object</tt> content type. On the producer side the exception will be deserialized and thrown as is, instead of the <tt>HttpOperationFailedException</tt>. The caused exception is required to be serialized. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>urlDecodeHeaders</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td c
 olspan="1" rowspan="1" class="confluenceTd"> If this option is enabled, then during binding from Netty to Camel <a shape="rect" href="message.html" title="Message">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 <tt>org.apache.camel.component.netty.http.NettyHttpBinding</tt> and therefore if you implement a custom <tt>org.apache.camel.component.netty.http.NettyHttpBinding</tt> then you would need to decode the headers accordingly to this option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>nettySharedHttpServer</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To use a shared <a shape="rect" href="netty-http.html" title="Netty HTTP">Netty HTTP</a> server. See <a shape="rect" href="netty-http-server-example.html" title="Netty HTTP Server Example">Netty HTTP Server Example</a> for more details. </td></
 tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>disableStreamCache</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Determines whether or not the raw input stream from Netty <tt>HttpRequest#getContent()</tt> 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 <tt>true</tt> 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. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>securityConfiguration</t
 t> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Consumer only</b>. Refers to a <tt>org.apache.camel.component.netty.http.NettyHttpSecurityConfiguration</tt> for configuring secure web resources. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>send503whenSuspended</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Consumer only</b>. Whether to send back HTTP status code 503 when the consumer has been suspended. If the option is <tt>false</tt> then the Netty Acceptor is unbound when the consumer is suspended, so clients cannot connect anymore. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Name </th><th colspan="1" rowspan="1" class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>chunkedMaxContentLength</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1mb</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Value in bytes the max content length per chunked frame received on the Netty HTTP server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>compression</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Allow using gzip/deflate for compression on the Netty HTTP server if the client supports it from the HTTP headers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>headerFilterStrategy</tt> </td><td colspan="1" rowspan="1" c
 lass="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> To use a custom  <tt>org.apache.camel.spi.HeaderFilterStrategy</tt> to filter headers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpMethodRestrict</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> To disable HTTP methods on the Netty HTTP consumer. You can specify multiple separated by comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>mapHeaders</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If this option is enabled, then during binding from Netty to Camel <a shape="rect" href="message.html" title="Message">Message</a> then the headers will be mapped as well (eg added as header to the Camel <a shape="rect" href="message.html" title="Message">Message</a> as well). You can turn off this option to disable
  this. The headers can still be accessed from the <tt>org.apache.camel.component.netty.http.NettyHttpMessage</tt> message with the method <tt>getHttpRequest()</tt> that returns the Netty HTTP request <tt>org.jboss.netty.handler.codec.http.HttpRequest</tt> instance. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>matchOnUriPrefix</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 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. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>nettyHttpBinding</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> To use a custom <tt>org.apache.camel.component.netty.http.NettyHttpBinding</tt> for binding to/from Netty and Camel Message API. </td></tr><tr><td colspan="1" row
 span="1" class="confluenceTd"> <tt>bridgeEndpoint</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If the option is <tt>true</tt>, the producer will ignore the <tt>Exchange.HTTP_URI</tt> header, and use the endpoint's URI for request. You may also set the <tt>throwExceptionOnFailure</tt> to be <tt>false</tt> to let the producer send all the fault response back. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>throwExceptionOnFailure</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to disable throwing the <tt>HttpOperationFailedException</tt> in case of failed responses from the remote server. This allows you to get all responses regardles of the HTTP status code. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>traceEnabled</tt> </td><td colspan="1" rowspan="1" class="confluenceTd
 "> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to enable HTTP TRACE for this Netty HTTP consumer. By default TRACE is turned off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>transferException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If enabled and an <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a <tt>application/x-java-serialized-object</tt> content type. On the producer side the exception will be deserialized and thrown as is, instead of the <tt>HttpOperationFailedException</tt>. The caused exception is required to be serialized. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>urlDecodeHeaders</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1
 " rowspan="1" class="confluenceTd"> If this option is enabled, then during binding from Netty to Camel <a shape="rect" href="message.html" title="Message">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 <tt>org.apache.camel.component.netty.http.NettyHttpBinding</tt> and therefore if you implement a custom <tt>org.apache.camel.component.netty.http.NettyHttpBinding</tt> then you would need to decode the headers accordingly to this option. <b>Notice:</b> This option is default <tt>true</tt> for Camel 2.12.x, and default <tt>false</tt> from Camel 2.13 onwards. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>nettySharedHttpServer</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To use a shared <a shape="rect" href="netty-http.html" title="Netty HTTP">Netty HTTP</a> server. See <a shape="rect" href="netty-ht
 tp-server-example.html" title="Netty HTTP Server Example">Netty HTTP Server Example</a> for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>disableStreamCache</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Determines whether or not the raw input stream from Netty <tt>HttpRequest#getContent()</tt> 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 <tt>true</tt> 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 t
 he Netty raw stream. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>securityConfiguration</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Consumer only</b>. Refers to a <tt>org.apache.camel.component.netty.http.NettyHttpSecurityConfiguration</tt> for configuring secure web resources. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>send503whenSuspended</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Consumer only</b>. Whether to send back HTTP status code 503 when the consumer has been suspended. If the option is <tt>false</tt> then the Netty Acceptor is unbound when the consumer is suspended, so clients cannot connect anymore. </td></tr></tbody></table>
 </div>
 </div>