Author: buildbot Date: Mon Jun 17 16:18:21 2013 New Revision: 865957 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 Mon Jun 17 16:18:21 2013 @@ -125,10 +125,28 @@ Notice that some options from <a shape=" <p>The following headers can be used on the producer to control the HTTP request.</p> <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"> Type </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelHttpMethod</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Allow to control what HTTP method to use such as GET, POST, TRACE etc. The type can also be a <tt>org.jboss.netty.handler.codec.http.HttpMethod</tt> instance. </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"> To set the content-type of the HTTP body. For example: <tt>text/plain; charset="UTF-8"</tt>. </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"> Type </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelHttpMethod</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Allow to control what HTTP method to use such as GET, POST, TRACE etc. The type can also be a <tt>org.jboss.netty.handler.codec.http.HttpMethod</tt> instance. </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"> Allows to provide URI query parameters as a <tt>String</tt> value that overrides the endpoint configuration. Separate multiple parameters using the & sign. For example: <tt> foo=bar&beer=yes</tt>. </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"> To set the content-type of the HTTP body. For example: <tt>text/plain; charset="UTF-8"</tt>. </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" title="Netty HTTP">Netty HTTP</a> endpoint:</p> + +<p>The description in the table takes offset in a route having: <tt>from("netty-http:http:0.0.0.0:8080/myapp")...</tt> </p> + +<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"> Type </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelHttpMethod</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The HTTP method used, such as GET, POST, TRACE etc. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelHttpUrl</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The URL including protocol, host and port, etc: +<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> +<pre class="code-java">http:<span class="code-comment">//0.0.0.0:8080/myapp</span></pre> +</div></div> +<p> </p></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"> +<pre class="code-java">/myapp</pre> +</div></div> +<p> </p></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"> The co ntent type if provided. For example: <tt>text/plain; charset="UTF-8"</tt>. </td></tr></tbody></table> +</div> +</div> + + <h3><a shape="rect" name="NettyHTTP-AccesstoNettytypes"></a>Access to Netty types</h3> <p>This component uses the <tt>org.apache.camel.component.netty.http.NettyHttpMessage</tt> as the message implementation on the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>. This allows end users to get access to the original Netty request/response instances if needed, as shown below:</p>