Author: buildbot
Date: Thu Jun 27 16:18:14 2013
New Revision: 867641
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
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/netty-http.html
==============================================================================
--- websites/production/camel/content/netty-http.html (original)
+++ websites/production/camel/content/netty-http.html Thu Jun 27 16:18:14 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>chunked</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Allow using chunked transfer if the client supports it
from the HTTP headers. </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 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" class="confluenceTd"> </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"> </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 acces
sed 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"> </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" rowspan="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> </t
d><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 colspan="1" ro
wspan="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></
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>chunked</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Allow using chunked transfer if the client supports it
from the HTTP headers. </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 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" class="confluenceTd"> </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"> </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 acces
sed 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"> </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" rowspan="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> </t
d><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 colspan="1" ro
wspan="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><t
r><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></tbody></table>
</div>
</div>
@@ -148,7 +148,7 @@ Notice that some options from <a shape="
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[http://0.0.0.0:8080/myapp]]></script>
</div></div> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelHttpUri</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>String</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The URI
without protocol, host and port, etc: <div class="code panel"
style="border-width: 1px;"><div class="codeContent panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[/myapp]]></script>
-</div></div> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelHttpQuery</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>String</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Any
query parameters, such as <tt>foo=bar&beer=yes</tt> </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelHttpPath</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Additional context-path. This
value is empty if the client called the context-path <tt>/myapp</tt>. If the
client calls <tt>/myapp/mystuff</tt>, then this header value is
<tt>/mystuff</tt>. In other words its the value after the context-path
configured on the route endpoint. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Content-Type</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> T
he content type if provided. For example: <tt>text/plain;
charset="UTF-8"</tt>. </td></tr></tbody></table>
+</div></div> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelHttpQuery</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>String</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Any
query parameters, such as <tt>foo=bar&beer=yes</tt> </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelHttpPath</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Additional context-path. This
value is empty if the client called the context-path <tt>/myapp</tt>. If the
client calls <tt>/myapp/mystuff</tt>, then this header value is
<tt>/mystuff</tt>. In other words its the value after the context-path
configured on the route endpoint. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelHttpCharacterEncoding</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1"
rowspan="1" class="co
nfluenceTd"> The charset from the content-type header. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>Content-Type</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The content type if provided. For
example: <tt>text/plain; charset="UTF-8"</tt>. </td></tr></tbody></table>
</div>
</div>
