camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r874892 - in /websites/production/camel/content: cache/main.pageCache camel-2120-release.html netty-http.html
Date Fri, 16 Aug 2013 14:19:20 GMT
Author: buildbot
Date: Fri Aug 16 14:19:19 2013
New Revision: 874892

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-2120-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-2120-release.html
==============================================================================
--- websites/production/camel/content/camel-2120-release.html (original)
+++ websites/production/camel/content/camel-2120-release.html Fri Aug 16 14:19:19 2013
@@ -94,7 +94,7 @@
 
 <p>Welcome to the 2.12.0 release which approx XXX issues resolved (new features, improvements
and bug fixes such as...)</p>
 
-<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint Annotations">Endpoint
Annotations</a> along with automatically created HTML documentation for the endpoint
parameters; this makes it easier for component developers to add a few refactoring-safe annotations
to their Endpoint or Consumer implementations and, (along with javadoc comments on the field
or setter method), get nice user documentation on how to use the endpoint for free.</li><li><a
shape="rect" href="componentconfiguration.html" title="ComponentConfiguration">ComponentConfiguration</a>
API provides a handy API for tools developers to introspect on a Component to find all the
possible parameters, their types and any extra annotations (like Bean Validation Annotations)
to be able to create/edit endpoints or URI strings so that tools can generate nicer UIs for
configuring endpoints than just letting folks edit Strings.</li><li><a shape="rect"
href="endpointcompleter.html" title="EndpointCompleter">Endpoi
 ntCompleter</a> API provides a hook so that command line tools (like <a shape="rect"
class="external-link" href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html">Karaf's
shell</a>), IDEs and web tools can get (bash tab like) auto-completion on endpoint paths
(such as file or directory names, message queue names, database table names) when creating
or using new endpoints</li><li>Reduced stack-frames in use during routing, that
also makes Camel's stack traces being logged much less verbose. This also allows people to
easier debug the internals of Camel as less <tt>AsyncCallback</tt> callbacks are
in use during routing.</li><li>Easy to use <a shape="rect" href="message-history.html"
title="Message History">Message History</a> out of the box. And included message
history as "route stack-trace" when exceptions logged by <a shape="rect" href="error-handler.html"
title="Error Handler">Error Handler</a> to make it easier for end users to spot where
the exception o
 ccurred.</li><li><a shape="rect" href="spring-web-services.html" title="Spring
Web Services">Spring Web Services</a> now supports setting/receiving SOAP headers
more easily using a header on the Camel <a shape="rect" href="message.html" title="Message">Message</a>.</li><li>Evaluating
<a shape="rect" href="groovy.html" title="Groovy">Groovy</a> expressions is faster
as we cache the compiled scripts.</li><li>Added <tt>base64</tt> option
to <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a>
to allow transferring security token over <a shape="rect" href="jms.html" title="JMS">JMS</a>
and other transports as base64 encoded representation.</li><li>Made it easier
to use <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a>
as the credentials can be provided in headers, when sending a message to a secured route.</li><li><a
shape="rect" href="bindy.html" title="Bindy">Bindy</a> now supports enums.</li><li>Added
new <a shape="re
 ct" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> to perform
live debugging of messages during routing. The <a shape="rect" href="backlogdebugger.html"
title="BacklogDebugger">BacklogDebugger</a> has JMX API allows tooling to control
the debugger.</li><li>While using the <a shape="rect" class="external-link"
href="http://xircles.codehaus.org/projects/jackson" rel="nofollow">Jackson library</a>
through the <a shape="rect" href="json.html" title="JSON">JSON</a> Dataformat
there's now a <tt>jsonView</tt> attribute you could make use of directly inside
the <a shape="rect" href="dsl.html" title="DSL">DSL</a> itself.</li><li><a
shape="rect" href="smpp.html" title="SMPP">SMPP</a> now supports optional parameters
in all commands where they are possible.</li><li><a shape="rect" href="jdbc.html"
title="JDBC">JDBC</a> now supports named parameters.</li><li>Added timeout
support for <a shape="rect" href="direct.html" title="Direct">Direct</a> producers
to wait for cons
 umer to become active.</li><li>Added <tt>stats</tt> action to <a
shape="rect" href="controlbus.html" title="ControlBus">ControlBus</a> to easily get
performance statics in a single XML message.</li><li>Added support for request
timeout on <a shape="rect" href="netty.html" title="Netty">Netty</a> producer,
and to configure logging level on <a shape="rect" href="netty.html" title="Netty">Netty</a>
consumer to be less noisy for ChannelClosedException which can flood the logs when client
disconnects abruptly.</li><li><a shape="rect" href="springbatch.html" title="SpringBatch">Spring
Batch</a> component producer now returns the <tt>JobExecution</tt> instance
as the output message. Users can use the <tt>JobExecution</tt> instance to perform
some operations using the Spring Batch API directly.</li><li>Added support for
NULL values in <a shape="rect" href="sql-component.html" title="SQL Component">SQL</a>
with named parameters.</li><li>Optimized <a shape="rect" href="jetty.html"
title="Jett
 y">Jetty</a> streaming responses in non-chunked mode; and as well using buffer sizes
based on <tt>HttpServletResponse.getBufferSize()</tt> instead of fixed size of
4kb.</li><li>Added <tt>greedy</tt> option to <a shape="rect" href="polling-consumer.html"
title="Polling Consumer">scheduled polling consumer</a>.</li><li>Added
support for accessing the length field on Java arrays in <a shape="rect" href="simple.html"
title="Simple">Simple</a> language.</li><li>Added support for using JAXB
annotations with Camel's Jackson <a shape="rect" href="json.html" title="JSON">JSON</a>
component.</li><li>Added the ability for <a shape="rect" href="bindy.html"
title="Bindy">Bindy</a> to skip content when parsing fixed-length records.</li><li><a
shape="rect" href="mongodb.html" title="MongoDB">MongoDB</a> now supports aggregation
queries.</li><li><a shape="rect" href="netty.html" title="Netty">Netty</a>
allows to use shared Netty boss and worker thread pools.</li><li>The <a shape="rect"
href="camel-
 maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a>
for component and data format now packages as OSGi bundles out of the box.</li><li>Easier
<a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a>
configuration using <tt>StreamCachingStrategy</tt>. Also allows spool directory
per <a shape="rect" href="camelcontext.html" title="CamelContext">CamelContext</a>
instead of shared per JVM. And insight at runtime using JMX management. As well allowing to
plugin 3rd party implementations.</li><li>Improved <a shape="rect" href="netty.html"
title="Netty">Netty</a> to be able to join an UDP multicast group.</li><li>Using
Camel <a shape="rect" href="spring.html" title="Spring">Spring</a> is now setting
up Camel routes later in the process allow Spring to complete all of its dependency injection,
before Camel <tt>RouteBuilder</tt> instances is configured. This allows to safely
use Spring dependency injection in these <tt>RouteBuilder</tt
 > classes.</li><li>Services in a <a shape="rect" href="camelcontext.html"
title="CamelContext">CamelContext</a> which can only be enlisted once (eg it similar
to a static in a JVM) has simpler and fixed MBean names in JMX.</li><li><a
shape="rect" href="sql-component.html" title="SQL Component">JDBC based aggregation repository</a>
for the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a>
EIP now supports optimistic locking, allows clustered Camel applications to use a shared database
for the aggregation repository.</li><li><a shape="rect" href="recipient-list.html"
title="Recipient List">Recipient List</a> stores a property (<tt>Exchange.RECIPIENT_LIST_ENDPOINT</tt>)
on the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> with
the <a shape="rect" href="uris.html" title="URIs">URIs</a> of the <a shape="rect"
href="endpoint.html" title="Endpoint">Endpoint</a> the message was sent to.</li><li>Added
<tt>mask</tt> option to <a shape="rect" href="
 camel-jmx.html" title="Camel JMX">Camel JMX</a> to hide sensitive information such
as passwords.</li><li>Added <tt>outputType</tt> option supporting
<tt>SelectList</tt>, and <tt>SelectOne</tt> to <a shape="rect"
href="sql-component.html" title="SQL Component">SQL Component</a> to dictate the
output message body type when doing SQL SELECT queries.</li><li><a shape="rect"
href="polling-consumer.html" title="Polling Consumer">Polling Consumer</a>s such
as <a shape="rect" href="file2.html" title="File2">File</a>, and <a shape="rect"
href="ftp2.html" title="FTP2">FTP</a> now supports using custom scheduler. Providing
a new <a shape="rect" href="quartz2.html" title="Quartz2">Quartz2</a>, and <a
shape="rect" href="spring.html" title="Spring">Spring</a> based out of the box, that
allows to use CRON based scheduler.</li><li><a shape="rect" href="polling-consumer.html"
title="Polling Consumer">Polling Consumer</a>s such as <a shape="rect" href="file2.html"
title="File2">File</a>, and <a shape
 ="rect" href="ftp2.html" title="FTP2">FTP</a> now supports <em>backoff</em>,
to let the consumer be less aggressive, when there has been no messages to poll, or errors
keeps occurring for a while.</li><li>Added support for XML Encryption 1.1 algorithms
in the <a shape="rect" href="xmlsecurity-dataformat.html" title="XMLSecurity DataFormat">XMLSecurity
data format</a>. It is now possible to specify stronger digest algorithms when using
RSA OAEP Key Transport algorithms.</li></ul>
+<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint Annotations">Endpoint
Annotations</a> along with automatically created HTML documentation for the endpoint
parameters; this makes it easier for component developers to add a few refactoring-safe annotations
to their Endpoint or Consumer implementations and, (along with javadoc comments on the field
or setter method), get nice user documentation on how to use the endpoint for free.</li><li><a
shape="rect" href="componentconfiguration.html" title="ComponentConfiguration">ComponentConfiguration</a>
API provides a handy API for tools developers to introspect on a Component to find all the
possible parameters, their types and any extra annotations (like Bean Validation Annotations)
to be able to create/edit endpoints or URI strings so that tools can generate nicer UIs for
configuring endpoints than just letting folks edit Strings.</li><li><a shape="rect"
href="endpointcompleter.html" title="EndpointCompleter">Endpoi
 ntCompleter</a> API provides a hook so that command line tools (like <a shape="rect"
class="external-link" href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html">Karaf's
shell</a>), IDEs and web tools can get (bash tab like) auto-completion on endpoint paths
(such as file or directory names, message queue names, database table names) when creating
or using new endpoints</li><li>Reduced stack-frames in use during routing, that
also makes Camel's stack traces being logged much less verbose. This also allows people to
easier debug the internals of Camel as less <tt>AsyncCallback</tt> callbacks are
in use during routing.</li><li>Easy to use <a shape="rect" href="message-history.html"
title="Message History">Message History</a> out of the box. And included message
history as "route stack-trace" when exceptions logged by <a shape="rect" href="error-handler.html"
title="Error Handler">Error Handler</a> to make it easier for end users to spot where
the exception o
 ccurred.</li><li><a shape="rect" href="spring-web-services.html" title="Spring
Web Services">Spring Web Services</a> now supports setting/receiving SOAP headers
more easily using a header on the Camel <a shape="rect" href="message.html" title="Message">Message</a>.</li><li>Evaluating
<a shape="rect" href="groovy.html" title="Groovy">Groovy</a> expressions is faster
as we cache the compiled scripts.</li><li>Added <tt>base64</tt> option
to <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a>
to allow transferring security token over <a shape="rect" href="jms.html" title="JMS">JMS</a>
and other transports as base64 encoded representation.</li><li>Made it easier
to use <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a>
as the credentials can be provided in headers, when sending a message to a secured route.</li><li><a
shape="rect" href="bindy.html" title="Bindy">Bindy</a> now supports enums.</li><li>Added
new <a shape="re
 ct" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> to perform
live debugging of messages during routing. The <a shape="rect" href="backlogdebugger.html"
title="BacklogDebugger">BacklogDebugger</a> has JMX API allows tooling to control
the debugger.</li><li>While using the <a shape="rect" class="external-link"
href="http://xircles.codehaus.org/projects/jackson" rel="nofollow">Jackson library</a>
through the <a shape="rect" href="json.html" title="JSON">JSON</a> Dataformat
there's now a <tt>jsonView</tt> attribute you could make use of directly inside
the <a shape="rect" href="dsl.html" title="DSL">DSL</a> itself.</li><li><a
shape="rect" href="smpp.html" title="SMPP">SMPP</a> now supports optional parameters
in all commands where they are possible.</li><li><a shape="rect" href="jdbc.html"
title="JDBC">JDBC</a> now supports named parameters.</li><li>Added timeout
support for <a shape="rect" href="direct.html" title="Direct">Direct</a> producers
to wait for cons
 umer to become active.</li><li>Added <tt>stats</tt> action to <a
shape="rect" href="controlbus.html" title="ControlBus">ControlBus</a> to easily get
performance statics in a single XML message.</li><li>Added support for request
timeout on <a shape="rect" href="netty.html" title="Netty">Netty</a> producer,
and to configure logging level on <a shape="rect" href="netty.html" title="Netty">Netty</a>
consumer to be less noisy for ChannelClosedException which can flood the logs when client
disconnects abruptly.</li><li><a shape="rect" href="springbatch.html" title="SpringBatch">Spring
Batch</a> component producer now returns the <tt>JobExecution</tt> instance
as the output message. Users can use the <tt>JobExecution</tt> instance to perform
some operations using the Spring Batch API directly.</li><li>Added support for
NULL values in <a shape="rect" href="sql-component.html" title="SQL Component">SQL</a>
with named parameters.</li><li>Optimized <a shape="rect" href="jetty.html"
title="Jett
 y">Jetty</a> streaming responses in non-chunked mode; and as well using buffer sizes
based on <tt>HttpServletResponse.getBufferSize()</tt> instead of fixed size of
4kb.</li><li>Added <tt>greedy</tt> option to <a shape="rect" href="polling-consumer.html"
title="Polling Consumer">scheduled polling consumer</a>.</li><li>Added
support for accessing the length field on Java arrays in <a shape="rect" href="simple.html"
title="Simple">Simple</a> language.</li><li>Added support for using JAXB
annotations with Camel's Jackson <a shape="rect" href="json.html" title="JSON">JSON</a>
component.</li><li>Added the ability for <a shape="rect" href="bindy.html"
title="Bindy">Bindy</a> to skip content when parsing fixed-length records.</li><li><a
shape="rect" href="mongodb.html" title="MongoDB">MongoDB</a> now supports aggregation
queries.</li><li><a shape="rect" href="netty.html" title="Netty">Netty</a>
allows to use shared Netty boss and worker thread pools.</li><li>The <a shape="rect"
href="camel-
 maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a>
for component and data format now packages as OSGi bundles out of the box.</li><li>Easier
<a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a>
configuration using <tt>StreamCachingStrategy</tt>. Also allows spool directory
per <a shape="rect" href="camelcontext.html" title="CamelContext">CamelContext</a>
instead of shared per JVM. And insight at runtime using JMX management. As well allowing to
plugin 3rd party implementations.</li><li>Improved <a shape="rect" href="netty.html"
title="Netty">Netty</a> to be able to join an UDP multicast group.</li><li>Using
Camel <a shape="rect" href="spring.html" title="Spring">Spring</a> is now setting
up Camel routes later in the process allow Spring to complete all of its dependency injection,
before Camel <tt>RouteBuilder</tt> instances is configured. This allows to safely
use Spring dependency injection in these <tt>RouteBuilder</tt
 > classes.</li><li>Services in a <a shape="rect" href="camelcontext.html"
title="CamelContext">CamelContext</a> which can only be enlisted once (eg it similar
to a static in a JVM) has simpler and fixed MBean names in JMX.</li><li><a
shape="rect" href="sql-component.html" title="SQL Component">JDBC based aggregation repository</a>
for the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a>
EIP now supports optimistic locking, allows clustered Camel applications to use a shared database
for the aggregation repository.</li><li><a shape="rect" href="recipient-list.html"
title="Recipient List">Recipient List</a> stores a property (<tt>Exchange.RECIPIENT_LIST_ENDPOINT</tt>)
on the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> with
the <a shape="rect" href="uris.html" title="URIs">URIs</a> of the <a shape="rect"
href="endpoint.html" title="Endpoint">Endpoint</a> the message was sent to.</li><li>Added
<tt>mask</tt> option to <a shape="rect" href="
 camel-jmx.html" title="Camel JMX">Camel JMX</a> to hide sensitive information such
as passwords.</li><li>Added <tt>outputType</tt> option supporting
<tt>SelectList</tt>, and <tt>SelectOne</tt> to <a shape="rect"
href="sql-component.html" title="SQL Component">SQL Component</a> to dictate the
output message body type when doing SQL SELECT queries.</li><li><a shape="rect"
href="polling-consumer.html" title="Polling Consumer">Polling Consumer</a>s such
as <a shape="rect" href="file2.html" title="File2">File</a>, and <a shape="rect"
href="ftp2.html" title="FTP2">FTP</a> now supports using custom scheduler. Providing
a new <a shape="rect" href="quartz2.html" title="Quartz2">Quartz2</a>, and <a
shape="rect" href="spring.html" title="Spring">Spring</a> based out of the box, that
allows to use CRON based scheduler.</li><li><a shape="rect" href="polling-consumer.html"
title="Polling Consumer">Polling Consumer</a>s such as <a shape="rect" href="file2.html"
title="File2">File</a>, and <a shape
 ="rect" href="ftp2.html" title="FTP2">FTP</a> now supports <em>backoff</em>,
to let the consumer be less aggressive, when there has been no messages to poll, or errors
keeps occurring for a while.</li><li>Added support for XML Encryption 1.1 algorithms
in the <a shape="rect" href="xmlsecurity-dataformat.html" title="XMLSecurity DataFormat">XMLSecurity
data format</a>. It is now possible to specify stronger digest algorithms when using
RSA OAEP Key Transport algorithms.</li><li><a shape="rect" href="netty.html"
title="Netty">Netty</a> consumer now unbinds/binds the acceptor when the route is
suspended/resumed.</li></ul>
 
 
 <h3><a shape="rect" name="Camel2.12.0Release-FixedIssues"></a>Fixed Issues</h3>

Modified: websites/production/camel/content/netty-http.html
==============================================================================
--- websites/production/camel/content/netty-http.html (original)
+++ websites/production/camel/content/netty-http.html Fri Aug 16 14:19:19 2013
@@ -126,7 +126,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></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"> <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>
 </div>
 </div>
 



Mime
View raw message