Author: buildbot
Date: Sun Apr 29 06:23:53 2012
New Revision: 814926

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 Sun Apr 29 
06:23:53 2012
@@ -8254,7 +8254,7 @@ jetty:http:<span class="code-comment">//
 
 <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. 
</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. 
</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. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>matchOnUriPrefix</t
 t> </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" rowspan="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 
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 (C
 amel 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>bridgeEndpoint</tt> </td><td colspan="1" rowspa
 n="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. 
</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="conf
 luenceTd"> <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" rowspan="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 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 
str
 eam 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>bridgeEndpoin
 t</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 value 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 cli
 ent. 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></tbody></table>
 </div>
 </div>
@@ -8566,16 +8566,19 @@ If the exchange failed with an exception
 
 <p>The following example shows how to customize the 
<tt>DefaultHttpBinding</tt> in order to change how exceptions are returned:</p>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
-<pre class="code-java"><span class="code-keyword">public</span> class 
MyJettyHttpBinding <span class="code-keyword">extends</span> 
DefaultJettyHttpBinding {
+<pre class="code-java"><span class="code-keyword">public</span> class 
MyHttpBinding <span class="code-keyword">extends</span> DefaultHttpBinding {
+    <span class="code-keyword">public</span> MyHttpBinding(HttpEndpoint ep) {
+        <span class="code-keyword">super</span>(ep);
+    }
     @Override
-    <span class="code-keyword">protected</span> void populateResponse(Exchange 
exchange, JettyContentExchange httpExchange, Message in,
-                                    HeaderFilterStrategy strategy, <span 
class="code-object">int</span> responseCode) <span 
class="code-keyword">throws</span> IOException {
-
-        Message answer = exchange.getOut();
-
-        answer.setHeaders(in.getHeaders());
-        answer.setHeader(Exchange.HTTP_RESPONSE_CODE, responseCode);
-        answer.setBody(<span class="code-quote">"Not exactly the message the 
server returned."</span>);
+    <span class="code-keyword">public</span> void 
doWriteExceptionResponse(Throwable exception, HttpServletResponse response) 
<span class="code-keyword">throws</span> IOException {
+        <span class="code-comment">// we override the doWriteExceptionResponse 
as we only want to alter the binding how exceptions is
+</span>        <span class="code-comment">// written back to the client. 
+</span>
+        <span class="code-comment">// we just <span 
class="code-keyword">return</span> HTTP 200 so the client thinks its okay
+</span>        response.setStatus(200);
+        <span class="code-comment">// and we <span 
class="code-keyword">return</span> <span class="code-keyword">this</span> fixed 
text
+</span>        response.getWriter().write(<span class="code-quote">"Something 
went wrong but we dont care"</span>);
     }
 }
 </pre>

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 Sun Apr 29 06:23:53 
2012
@@ -28493,7 +28493,7 @@ jetty:http:<span class="code-comment">//
 
 <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. 
</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. 
</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. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>matchOnUriPrefix</t
 t> </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" rowspan="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 
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 wil
 l 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>bridgeEndpoint</tt> </td><td colspan="1" rowspan="1" 
cl
 ass="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. 
</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="conf
 luenceTd"> <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" rowspan="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 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 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>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 value 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 cli
 ent. 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></tbody></table>
 </div>
 </div>
@@ -28805,16 +28805,19 @@ If the exchange failed with an exception
 
 <p>The following example shows how to customize the 
<tt>DefaultHttpBinding</tt> in order to change how exceptions are returned:</p>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
-<pre class="code-java"><span class="code-keyword">public</span> class 
MyJettyHttpBinding <span class="code-keyword">extends</span> 
DefaultJettyHttpBinding {
+<pre class="code-java"><span class="code-keyword">public</span> class 
MyHttpBinding <span class="code-keyword">extends</span> DefaultHttpBinding {
+    <span class="code-keyword">public</span> MyHttpBinding(HttpEndpoint ep) {
+        <span class="code-keyword">super</span>(ep);
+    }
     @Override
-    <span class="code-keyword">protected</span> void populateResponse(Exchange 
exchange, JettyContentExchange httpExchange, Message in,
-                                    HeaderFilterStrategy strategy, <span 
class="code-object">int</span> responseCode) <span 
class="code-keyword">throws</span> IOException {
-
-        Message answer = exchange.getOut();
-
-        answer.setHeaders(in.getHeaders());
-        answer.setHeader(Exchange.HTTP_RESPONSE_CODE, responseCode);
-        answer.setBody(<span class="code-quote">"Not exactly the message the 
server returned."</span>);
+    <span class="code-keyword">public</span> void 
doWriteExceptionResponse(Throwable exception, HttpServletResponse response) 
<span class="code-keyword">throws</span> IOException {
+        <span class="code-comment">// we override the doWriteExceptionResponse 
as we only want to alter the binding how exceptions is
+</span>        <span class="code-comment">// written back to the client. 
+</span>
+        <span class="code-comment">// we just <span 
class="code-keyword">return</span> HTTP 200 so the client thinks its okay
+</span>        response.setStatus(200);
+        <span class="code-comment">// and we <span 
class="code-keyword">return</span> <span class="code-keyword">this</span> fixed 
text
+</span>        response.getWriter().write(<span class="code-quote">"Something 
went wrong but we dont care"</span>);
     }
 }
 </pre>

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 Sun Apr 29 06:23:53 2012
@@ -98,7 +98,7 @@ jetty:http:<span class="code-comment">//
 
 <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. 
</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. 
</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. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>matchOnUriPrefix</t
 t> </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" rowspan="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 
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 t
 he 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>bridgeEndpoint</tt> </td><td colspan="1" rowspan="1" 
class="con
 fluenceTd"> <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. 
</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="conf
 luenceTd"> <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" rowspan="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 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 i
 s 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>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 value 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 cli
 ent. 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></tbody></table>
 </div>
 </div>
@@ -410,16 +410,19 @@ If the exchange failed with an exception
 
 <p>The following example shows how to customize the 
<tt>DefaultHttpBinding</tt> in order to change how exceptions are returned:</p>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
-<pre class="code-java"><span class="code-keyword">public</span> class 
MyJettyHttpBinding <span class="code-keyword">extends</span> 
DefaultJettyHttpBinding {
+<pre class="code-java"><span class="code-keyword">public</span> class 
MyHttpBinding <span class="code-keyword">extends</span> DefaultHttpBinding {
+    <span class="code-keyword">public</span> MyHttpBinding(HttpEndpoint ep) {
+        <span class="code-keyword">super</span>(ep);
+    }
     @Override
-    <span class="code-keyword">protected</span> void populateResponse(Exchange 
exchange, JettyContentExchange httpExchange, Message in,
-                                    HeaderFilterStrategy strategy, <span 
class="code-object">int</span> responseCode) <span 
class="code-keyword">throws</span> IOException {
-
-        Message answer = exchange.getOut();
-
-        answer.setHeaders(in.getHeaders());
-        answer.setHeader(Exchange.HTTP_RESPONSE_CODE, responseCode);
-        answer.setBody(<span class="code-quote">"Not exactly the message the 
server returned."</span>);
+    <span class="code-keyword">public</span> void 
doWriteExceptionResponse(Throwable exception, HttpServletResponse response) 
<span class="code-keyword">throws</span> IOException {
+        <span class="code-comment">// we override the doWriteExceptionResponse 
as we only want to alter the binding how exceptions is
+</span>        <span class="code-comment">// written back to the client. 
+</span>
+        <span class="code-comment">// we just <span 
class="code-keyword">return</span> HTTP 200 so the client thinks its okay
+</span>        response.setStatus(200);
+        <span class="code-comment">// and we <span 
class="code-keyword">return</span> <span class="code-keyword">this</span> fixed 
text
+</span>        response.getWriter().write(<span class="code-quote">"Something 
went wrong but we dont care"</span>);
     }
 }
 </pre>


Reply via email to