camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r873452 - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache jetty.html
Date Thu, 08 Aug 2013 11:21:41 GMT
Author: buildbot
Date: Thu Aug  8 11:21:41 2013
New Revision: 873452

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-component-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/jetty.html

Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Thu Aug  8 11:21:41 2013
@@ -8584,7 +8584,7 @@ jetty:http://hostname[:port][/resourceUr
 
 <h3><a shape="rect" name="BookComponentAppendix-Options"></a>Options</h3>
 <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>sessionSupport</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to enable the session manager on the server side of Jetty. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient.XXX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Configuration of Jetty's <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Tutorial/HttpClient" rel="nofollow">HttpClient</a>. For example, setting <tt>httpClient.idleTimeout=30000</tt> sets the idle timeout to 30 seconds. And <tt>httpCli
 ent.timeout=30000</tt> sets the request timeout to 30 seconds, in case you want to timeout sooner if you have long running request/response calls. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To use a shared <tt>org.eclipse.jetty.client.HttpClient</tt> for all producers created by this endpoint. This option should only be used in special circumstances. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMinThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for minimum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td 
 colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMaxThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for maximum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpBindingRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Reference to an <tt>org.apache.camel.component.http.HttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>HttpBinding</tt> can be used to customize how a response should be written for the consumer. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>jettyHttpBindingRef</tt> </td><td
  colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6.0+:</b> Reference to an <tt>org.apache.camel.component.jetty.JettyHttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>JettyHttpBinding</tt> can be used to customize how a response should be written for the producer. </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 the <tt>CamelServlet</tt> should try to find a target consumer by matching the URI prefix if no exact match is found. See here <a shape="rect" href="how-do-i-let-jetty-match-wildcards.html" title="How do I let Jetty match wildcards">How do I let Jetty match wildcards</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>handlers</tt> </td><td colspan="1" ro
 wspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies a comma-delimited set of <tt>org.mortbay.jetty.Handler</tt> instances in your <a shape="rect" href="registry.html" title="Registry">Registry</a> (such as your Spring <tt>ApplicationContext</tt>). These handlers are added to the Jetty servlet context (for example, to add security). </td></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"> <b>Camel 2.2:</b> If this option is false Jetty servlet will disable the HTTP streaming and set the content-length header on the response </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>enableJmx</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.3:</b> If this option is true, Jetty JMX s
 upport will be enabled for this endpoint. See <a shape="rect" href="#BookComponentAppendix-JettyJMXsupport">Jetty JMX support</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"> <b>Camel 2.3:</b> Determines whether or not the raw input stream from Jetty is cached or not (Camel will read the stream into a in memory/overflow to file, <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a>) cache. By default Camel will cache the Jetty 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. DefaultHttpBinding will copy the request input stream into a stream c
 ache and put it into message body if this option is <tt>false</tt> to support reading the stream multiple times. If you use <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. </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>transferException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b>  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>bridgeEndpoint</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the <b>throwExceptionOnFailure</b> to be false to let the HttpProducer send all the fault response back. <br clear="none" class="atl-forced-newline">
+<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>sessionSupport</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to enable the session manager on the server side of Jetty. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient.XXX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Configuration of Jetty's <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Tutorial/HttpClient" rel="nofollow">HttpClient</a>. For example, setting <tt>httpClient.idleTimeout=30000</tt> sets the idle timeout to 30 seconds. And <tt>httpCli
 ent.timeout=30000</tt> sets the request timeout to 30 seconds, in case you want to timeout sooner if you have long running request/response calls. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To use a shared <tt>org.eclipse.jetty.client.HttpClient</tt> for all producers created by this endpoint. This option should only be used in special circumstances. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMinThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for minimum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td 
 colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMaxThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for maximum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpBindingRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Reference to an <tt>org.apache.camel.component.http.HttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>HttpBinding</tt> can be used to customize how a response should be written for the consumer. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>jettyHttpBindingRef</tt> </td><td
  colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6.0+:</b> Reference to an <tt>org.apache.camel.component.jetty.JettyHttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>JettyHttpBinding</tt> can be used to customize how a response should be written for the producer. </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 the <tt>CamelServlet</tt> should try to find a target consumer by matching the URI prefix if no exact match is found. See here <a shape="rect" href="how-do-i-let-jetty-match-wildcards.html" title="How do I let Jetty match wildcards">How do I let Jetty match wildcards</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>handlers</tt> </td><td colspan="1" ro
 wspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies a comma-delimited set of <tt>org.mortbay.jetty.Handler</tt> instances in your <a shape="rect" href="registry.html" title="Registry">Registry</a> (such as your Spring <tt>ApplicationContext</tt>). These handlers are added to the Jetty servlet context (for example, to add security). <b>Important:</b> You can not use different handlers with different Jetty endpoints using the same port number. The handlers is associated to the port number. If you need different handlers, then use different port numbers. </td></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"> <b>Camel 2.2:</b> If this option is false Jetty servlet will disable the HTTP streaming and set the content-length header on the response </td></tr><tr><td colspan="1" rowspan
 ="1" class="confluenceTd"> <tt>enableJmx</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.3:</b> If this option is true, Jetty JMX support will be enabled for this endpoint. See <a shape="rect" href="#BookComponentAppendix-JettyJMXsupport">Jetty JMX support</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"> <b>Camel 2.3:</b> Determines whether or not the raw input stream from Jetty is cached or not (Camel will read the stream into a in memory/overflow to file, <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a>) cache. By default Camel will cache the Jetty input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you c
 an 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. DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is <tt>false</tt> to support reading the stream multiple times. If you use <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. </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 cols
 pan="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"> <b>Camel 2.6:</b>  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>bridgeEndpoint</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for reque
 st. You may also set the <b>throwExceptionOnFailure</b> to be false to let the HttpProducer send all the fault response back. <br clear="none" class="atl-forced-newline">
 <b>Camel 2.3:</b> If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". Also consider setting <b>disableStreamCache</b> to true to optimize when bridging. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>enableMultipartFilter</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5:</b> Whether Jetty <tt>org.eclipse.jetty.servlets.MultiPartFilter</tt> is enabled or not. You should set this value to <tt>false</tt> when bridging endpoints, to ensure multipart requests is proxied/bridged as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>multipartFilterRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b> Allows using a custom multipart filter. Note: setting <tt>multipartFilterRef</tt> forces the val
 ue of <tt>enableMultipartFilter</tt> to <tt>true</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>filtersRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> Allows using a custom filters which is putted into a list and can be find in the <a shape="rect" href="registry.html" title="Registry">Registry</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>continuationTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b> Allows to set a timeout in millis when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> as consumer (server). By default Jetty uses 30000. You can use a value of <tt>&lt;= 0</tt> to never expire. If a timeout occurs then the request will be expired and Jetty will return back a http error 503 to the client. This option
  is only in use when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> with the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>useContinuation</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b> Whether or not to use <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Feature/Continuations" rel="nofollow">Jetty continuations</a> for the Jetty Server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>sslContextParametersRef</tt><br clear="none" class="atl-forced-newline"> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt><br clear="none" class="atl-forced-newline"> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> Reference to a <tt>org.apache.camel.util
 .jsse.SSLContextParameters</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>.&#160; This reference overrides any configured SSLContextParameters at the component level.&#160; See <a shape="rect" href="#BookComponentAppendix-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. </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 Jetty consumer. By default TRACE is turned off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>headerFilterStrategy</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Reference to a instance of <tt>org.apache.camel.spi.HeaderFilterStrategy</tt> in the <a shape="rect" href="registry.html" ti
 tle="Registry">Registry</a>. It will be used to apply the custom headerFilterStrategy on the new create HttpJettyEndpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>urlRewrite</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b> Refers to a custom <tt>org.apache.camel.component.http.UrlRewrite</tt> which allows you to rewrite urls when you bridge/proxy endpoints. See more details at <a shape="rect" href="urlrewrite.html" title="UrlRewrite">UrlRewrite</a> and <a shape="rect" href="how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html" title="How to use Camel as a HTTP proxy between a client and server">How to use Camel as a HTTP proxy between a client and server</a>. </td></tr></tbody></table>
 </div>
 </div>

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Thu Aug  8 11:21:41 2013
@@ -1286,7 +1286,7 @@ jgroups://clusterName
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 nmr://serviceName
 ]]></script>
-</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Apache </td><td colspan="1" rowspan="1" class="confluenceTd"> Integration with the Normalized Message Router BUS in <a shape="rect" class="external-link" href="http://servicemix.apache.org/SMX4NMR/index.html">ServiceMix 4.x</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <span class="error">[rcode]</span> / camel-rcode in <a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">camel-extra</a>
+</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Apache </td><td colspan="1" rowspan="1" class="confluenceTd"> Integration with the Normalized Message Router BUS in <a shape="rect" class="external-link" href="http://servicemix.apache.org/SMX4NMR/index.html">ServiceMix 4.x</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="rcode.html" title="rcode">rcode</a> / camel-rcode in <a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">camel-extra</a>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 rcode://host[:port]/operation[?options]
@@ -30003,7 +30003,7 @@ jetty:http://hostname[:port][/resourceUr
 
 <h3><a shape="rect" name="BookInOnePage-Options"></a>Options</h3>
 <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>sessionSupport</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to enable the session manager on the server side of Jetty. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient.XXX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Configuration of Jetty's <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Tutorial/HttpClient" rel="nofollow">HttpClient</a>. For example, setting <tt>httpClient.idleTimeout=30000</tt> sets the idle timeout to 30 seconds. And <tt>httpCli
 ent.timeout=30000</tt> sets the request timeout to 30 seconds, in case you want to timeout sooner if you have long running request/response calls. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To use a shared <tt>org.eclipse.jetty.client.HttpClient</tt> for all producers created by this endpoint. This option should only be used in special circumstances. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMinThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for minimum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td 
 colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMaxThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for maximum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpBindingRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Reference to an <tt>org.apache.camel.component.http.HttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>HttpBinding</tt> can be used to customize how a response should be written for the consumer. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>jettyHttpBindingRef</tt> </td><td
  colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6.0+:</b> Reference to an <tt>org.apache.camel.component.jetty.JettyHttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>JettyHttpBinding</tt> can be used to customize how a response should be written for the producer. </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 the <tt>CamelServlet</tt> should try to find a target consumer by matching the URI prefix if no exact match is found. See here <a shape="rect" href="how-do-i-let-jetty-match-wildcards.html" title="How do I let Jetty match wildcards">How do I let Jetty match wildcards</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>handlers</tt> </td><td colspan="1" ro
 wspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies a comma-delimited set of <tt>org.mortbay.jetty.Handler</tt> instances in your <a shape="rect" href="registry.html" title="Registry">Registry</a> (such as your Spring <tt>ApplicationContext</tt>). These handlers are added to the Jetty servlet context (for example, to add security). </td></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"> <b>Camel 2.2:</b> If this option is false Jetty servlet will disable the HTTP streaming and set the content-length header on the response </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>enableJmx</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.3:</b> If this option is true, Jetty JMX s
 upport will be enabled for this endpoint. See <a shape="rect" href="#BookInOnePage-JettyJMXsupport">Jetty JMX support</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"> <b>Camel 2.3:</b> Determines whether or not the raw input stream from Jetty is cached or not (Camel will read the stream into a in memory/overflow to file, <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a>) cache. By default Camel will cache the Jetty 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. DefaultHttpBinding will copy the request input stream into a stream cache and
  put it into message body if this option is <tt>false</tt> to support reading the stream multiple times. If you use <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. </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>transferException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b>  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>bridgeEndpoint</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the <b>throwExceptionOnFailure</b> to be false to let the HttpProducer send all the fault response back. <br clear="none" class="atl-forced-newline">
+<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>sessionSupport</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to enable the session manager on the server side of Jetty. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient.XXX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Configuration of Jetty's <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Tutorial/HttpClient" rel="nofollow">HttpClient</a>. For example, setting <tt>httpClient.idleTimeout=30000</tt> sets the idle timeout to 30 seconds. And <tt>httpCli
 ent.timeout=30000</tt> sets the request timeout to 30 seconds, in case you want to timeout sooner if you have long running request/response calls. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To use a shared <tt>org.eclipse.jetty.client.HttpClient</tt> for all producers created by this endpoint. This option should only be used in special circumstances. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMinThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for minimum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td 
 colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMaxThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for maximum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpBindingRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Reference to an <tt>org.apache.camel.component.http.HttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>HttpBinding</tt> can be used to customize how a response should be written for the consumer. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>jettyHttpBindingRef</tt> </td><td
  colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6.0+:</b> Reference to an <tt>org.apache.camel.component.jetty.JettyHttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>JettyHttpBinding</tt> can be used to customize how a response should be written for the producer. </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 the <tt>CamelServlet</tt> should try to find a target consumer by matching the URI prefix if no exact match is found. See here <a shape="rect" href="how-do-i-let-jetty-match-wildcards.html" title="How do I let Jetty match wildcards">How do I let Jetty match wildcards</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>handlers</tt> </td><td colspan="1" ro
 wspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies a comma-delimited set of <tt>org.mortbay.jetty.Handler</tt> instances in your <a shape="rect" href="registry.html" title="Registry">Registry</a> (such as your Spring <tt>ApplicationContext</tt>). These handlers are added to the Jetty servlet context (for example, to add security). <b>Important:</b> You can not use different handlers with different Jetty endpoints using the same port number. The handlers is associated to the port number. If you need different handlers, then use different port numbers. </td></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"> <b>Camel 2.2:</b> If this option is false Jetty servlet will disable the HTTP streaming and set the content-length header on the response </td></tr><tr><td colspan="1" rowspan
 ="1" class="confluenceTd"> <tt>enableJmx</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.3:</b> If this option is true, Jetty JMX support will be enabled for this endpoint. See <a shape="rect" href="#BookInOnePage-JettyJMXsupport">Jetty JMX support</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"> <b>Camel 2.3:</b> Determines whether or not the raw input stream from Jetty is cached or not (Camel will read the stream into a in memory/overflow to file, <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a>) cache. By default Camel will cache the Jetty input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set t
 his 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. DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is <tt>false</tt> to support reading the stream multiple times. If you use <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. </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>transferException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b>  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>bridgeEndpoint</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You 
 may also set the <b>throwExceptionOnFailure</b> to be false to let the HttpProducer send all the fault response back. <br clear="none" class="atl-forced-newline">
 <b>Camel 2.3:</b> If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". Also consider setting <b>disableStreamCache</b> to true to optimize when bridging. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>enableMultipartFilter</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5:</b> Whether Jetty <tt>org.eclipse.jetty.servlets.MultiPartFilter</tt> is enabled or not. You should set this value to <tt>false</tt> when bridging endpoints, to ensure multipart requests is proxied/bridged as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>multipartFilterRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b> Allows using a custom multipart filter. Note: setting <tt>multipartFilterRef</tt> forces the val
 ue of <tt>enableMultipartFilter</tt> to <tt>true</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>filtersRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> Allows using a custom filters which is putted into a list and can be find in the <a shape="rect" href="registry.html" title="Registry">Registry</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>continuationTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b> Allows to set a timeout in millis when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> as consumer (server). By default Jetty uses 30000. You can use a value of <tt>&lt;= 0</tt> to never expire. If a timeout occurs then the request will be expired and Jetty will return back a http error 503 to the client. This option
  is only in use when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> with the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>useContinuation</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b> Whether or not to use <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Feature/Continuations" rel="nofollow">Jetty continuations</a> for the Jetty Server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>sslContextParametersRef</tt><br clear="none" class="atl-forced-newline"> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt><br clear="none" class="atl-forced-newline"> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> Reference to a <tt>org.apache.camel.util
 .jsse.SSLContextParameters</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>.&#160; This reference overrides any configured SSLContextParameters at the component level.&#160; See <a shape="rect" href="#BookInOnePage-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. </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 Jetty consumer. By default TRACE is turned off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>headerFilterStrategy</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Reference to a instance of <tt>org.apache.camel.spi.HeaderFilterStrategy</tt> in the <a shape="rect" href="registry.html" title="Reg
 istry">Registry</a>. It will be used to apply the custom headerFilterStrategy on the new create HttpJettyEndpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>urlRewrite</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b> Refers to a custom <tt>org.apache.camel.component.http.UrlRewrite</tt> which allows you to rewrite urls when you bridge/proxy endpoints. See more details at <a shape="rect" href="urlrewrite.html" title="UrlRewrite">UrlRewrite</a> and <a shape="rect" href="how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html" title="How to use Camel as a HTTP proxy between a client and server">How to use Camel as a HTTP proxy between a client and server</a>. </td></tr></tbody></table>
 </div>
 </div>

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

Modified: websites/production/camel/content/jetty.html
==============================================================================
--- websites/production/camel/content/jetty.html (original)
+++ websites/production/camel/content/jetty.html Thu Aug  8 11:21:41 2013
@@ -118,7 +118,7 @@ jetty:http://hostname[:port][/resourceUr
 
 <h3><a shape="rect" name="Jetty-Options"></a>Options</h3>
 <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>sessionSupport</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to enable the session manager on the server side of Jetty. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient.XXX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Configuration of Jetty's <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Tutorial/HttpClient" rel="nofollow">HttpClient</a>. For example, setting <tt>httpClient.idleTimeout=30000</tt> sets the idle timeout to 30 seconds. And <tt>httpCli
 ent.timeout=30000</tt> sets the request timeout to 30 seconds, in case you want to timeout sooner if you have long running request/response calls. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To use a shared <tt>org.eclipse.jetty.client.HttpClient</tt> for all producers created by this endpoint. This option should only be used in special circumstances. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMinThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for minimum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td 
 colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMaxThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for maximum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpBindingRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Reference to an <tt>org.apache.camel.component.http.HttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>HttpBinding</tt> can be used to customize how a response should be written for the consumer. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>jettyHttpBindingRef</tt> </td><td
  colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6.0+:</b> Reference to an <tt>org.apache.camel.component.jetty.JettyHttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>JettyHttpBinding</tt> can be used to customize how a response should be written for the producer. </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 the <tt>CamelServlet</tt> should try to find a target consumer by matching the URI prefix if no exact match is found. See here <a shape="rect" href="how-do-i-let-jetty-match-wildcards.html" title="How do I let Jetty match wildcards">How do I let Jetty match wildcards</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>handlers</tt> </td><td colspan="1" ro
 wspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies a comma-delimited set of <tt>org.mortbay.jetty.Handler</tt> instances in your <a shape="rect" href="registry.html" title="Registry">Registry</a> (such as your Spring <tt>ApplicationContext</tt>). These handlers are added to the Jetty servlet context (for example, to add security). </td></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"> <b>Camel 2.2:</b> If this option is false Jetty servlet will disable the HTTP streaming and set the content-length header on the response </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>enableJmx</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.3:</b> If this option is true, Jetty JMX s
 upport will be enabled for this endpoint. See <a shape="rect" href="#Jetty-JettyJMXsupport">Jetty JMX support</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"> <b>Camel 2.3:</b> Determines whether or not the raw input stream from Jetty is cached or not (Camel will read the stream into a in memory/overflow to file, <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a>) cache. By default Camel will cache the Jetty 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. DefaultHttpBinding will copy the request input stream into a stream cache and put it 
 into message body if this option is <tt>false</tt> to support reading the stream multiple times. If you use <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. </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>transferException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b>  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>bridgeEndpoint</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the <b>throwExceptionOnFailure</b> to be false to let the HttpProducer send all the fault response back. <br clear="none" class="atl-forced-newline">
+<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>sessionSupport</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to enable the session manager on the server side of Jetty. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient.XXX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Configuration of Jetty's <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Tutorial/HttpClient" rel="nofollow">HttpClient</a>. For example, setting <tt>httpClient.idleTimeout=30000</tt> sets the idle timeout to 30 seconds. And <tt>httpCli
 ent.timeout=30000</tt> sets the request timeout to 30 seconds, in case you want to timeout sooner if you have long running request/response calls. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClient</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To use a shared <tt>org.eclipse.jetty.client.HttpClient</tt> for all producers created by this endpoint. This option should only be used in special circumstances. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMinThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for minimum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td 
 colspan="1" rowspan="1" class="confluenceTd"> <tt>httpClientMaxThreads</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b>: To set a value for maximum number of threads in <tt>HttpClient</tt> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>httpBindingRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Reference to an <tt>org.apache.camel.component.http.HttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>HttpBinding</tt> can be used to customize how a response should be written for the consumer. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>jettyHttpBindingRef</tt> </td><td
  colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6.0+:</b> Reference to an <tt>org.apache.camel.component.jetty.JettyHttpBinding</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <tt>JettyHttpBinding</tt> can be used to customize how a response should be written for the producer. </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 the <tt>CamelServlet</tt> should try to find a target consumer by matching the URI prefix if no exact match is found. See here <a shape="rect" href="how-do-i-let-jetty-match-wildcards.html" title="How do I let Jetty match wildcards">How do I let Jetty match wildcards</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>handlers</tt> </td><td colspan="1" ro
 wspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies a comma-delimited set of <tt>org.mortbay.jetty.Handler</tt> instances in your <a shape="rect" href="registry.html" title="Registry">Registry</a> (such as your Spring <tt>ApplicationContext</tt>). These handlers are added to the Jetty servlet context (for example, to add security). <b>Important:</b> You can not use different handlers with different Jetty endpoints using the same port number. The handlers is associated to the port number. If you need different handlers, then use different port numbers. </td></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"> <b>Camel 2.2:</b> If this option is false Jetty servlet will disable the HTTP streaming and set the content-length header on the response </td></tr><tr><td colspan="1" rowspan
 ="1" class="confluenceTd"> <tt>enableJmx</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.3:</b> If this option is true, Jetty JMX support will be enabled for this endpoint. See <a shape="rect" href="#Jetty-JettyJMXsupport">Jetty JMX support</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"> <b>Camel 2.3:</b> Determines whether or not the raw input stream from Jetty is cached or not (Camel will read the stream into a in memory/overflow to file, <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a>) cache. By default Camel will cache the Jetty input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this opti
 on 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. DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is <tt>false</tt> to support reading the stream multiple times. If you use <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. </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>transferException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b>  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>bridgeEndpoint</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also
  set the <b>throwExceptionOnFailure</b> to be false to let the HttpProducer send all the fault response back. <br clear="none" class="atl-forced-newline">
 <b>Camel 2.3:</b> If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". Also consider setting <b>disableStreamCache</b> to true to optimize when bridging. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>enableMultipartFilter</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5:</b> Whether Jetty <tt>org.eclipse.jetty.servlets.MultiPartFilter</tt> is enabled or not. You should set this value to <tt>false</tt> when bridging endpoints, to ensure multipart requests is proxied/bridged as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>multipartFilterRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b> Allows using a custom multipart filter. Note: setting <tt>multipartFilterRef</tt> forces the val
 ue of <tt>enableMultipartFilter</tt> to <tt>true</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>filtersRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> Allows using a custom filters which is putted into a list and can be find in the <a shape="rect" href="registry.html" title="Registry">Registry</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>continuationTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b> Allows to set a timeout in millis when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> as consumer (server). By default Jetty uses 30000. You can use a value of <tt>&lt;= 0</tt> to never expire. If a timeout occurs then the request will be expired and Jetty will return back a http error 503 to the client. This option
  is only in use when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> with the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>useContinuation</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.6:</b> Whether or not to use <a shape="rect" class="external-link" href="http://wiki.eclipse.org/Jetty/Feature/Continuations" rel="nofollow">Jetty continuations</a> for the Jetty Server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>sslContextParametersRef</tt><br clear="none" class="atl-forced-newline"> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt><br clear="none" class="atl-forced-newline"> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> Reference to a <tt>org.apache.camel.util
 .jsse.SSLContextParameters</tt> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>.&#160; This reference overrides any configured SSLContextParameters at the component level.&#160; See <a shape="rect" href="#Jetty-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. </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 Jetty consumer. By default TRACE is turned off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>headerFilterStrategy</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Reference to a instance of <tt>org.apache.camel.spi.HeaderFilterStrategy</tt> in the <a shape="rect" href="registry.html" title="Registry">R
 egistry</a>. It will be used to apply the custom headerFilterStrategy on the new create HttpJettyEndpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>urlRewrite</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> <b>Producer only</b> Refers to a custom <tt>org.apache.camel.component.http.UrlRewrite</tt> which allows you to rewrite urls when you bridge/proxy endpoints. See more details at <a shape="rect" href="urlrewrite.html" title="UrlRewrite">UrlRewrite</a> and <a shape="rect" href="how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html" title="How to use Camel as a HTTP proxy between a client and server">How to use Camel as a HTTP proxy between a client and server</a>. </td></tr></tbody></table>
 </div>
 </div>



Mime
View raw message