camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r901542 [2/8] - in /websites/production/camel/content: ./ cache/
Date Fri, 14 Mar 2014 10:20:21 GMT
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 Fri Mar 14 10:20:20 2014
@@ -1528,11 +1528,11 @@ template.send("direct:alias-verify&
                     </div>
     </div>
 <p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1393618742354 {padding: 0px;}
-div.rbtoc1393618742354 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1393618742354 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1394792320297 {padding: 0px;}
+div.rbtoc1394792320297 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1394792320297 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1393618742354">
+/*]]>*/</style></p><div class="toc-macro rbtoc1394792320297">
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF Component</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>
@@ -3110,7 +3110,7 @@ private static class ProcessReport imple
 }
 ]]></script>
 </div></div><h4 id="BookComponentAppendix-WritetosubdirectoryusingExchange.FILE_NAME">Write to subdirectory using <code>Exchange.FILE_NAME</code></h4><p>Using a single route, it is possible to write a file to any number of subdirectories. If you have a route setup as such:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[  &lt;route&gt;
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[  &lt;route&gt;
     &lt;from uri=&quot;bean:myBean&quot;/&gt;
     &lt;to uri=&quot;file:/rootDirectory&quot;/&gt;
   &lt;/route&gt;
@@ -3119,7 +3119,11 @@ private static class ProcessReport imple
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[Exchange.FILE_NAME = hello.txt =&gt; /rootDirectory/hello.txt
 Exchange.FILE_NAME = foo/bye.txt =&gt; /rootDirectory/foo/bye.txt
 ]]></script>
-</div></div><p>This allows you to have a single route to write files to multiple destinations.</p><h4 id="BookComponentAppendix-Usingexpressionforfilenames">Using expression for filenames</h4><p>In this sample we want to move consumed files to a backup folder using today's date as a sub-folder name:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>This allows you to have a single route to write files to multiple destinations.</p><h4 id="BookComponentAppendix-Writingfilethroughthetemporarydirectoryrelativetothefinaldestination">Writing file through the temporary directory relative to the final destination</h4><p>Sometime you need to temporarily write the files to some directory relative to the destination directory. Such situation usually happens when some external process with limited filtering capabilities is reading from the directory you are writing to. In the example below files will be written to the&#160; <code>/var/myapp/filesInProgress</code> directory and after data transfer is done, they will be atomically moved to the<code>&#160;/var/myapp/finalDirectory </code>directory.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from(&quot;direct:start&quot;).
+  to(&quot;file:///var/myapp/finalDirectory?tempPrefix=/../filesInProgress/&quot;);
+]]></script>
+</div></div><h4 id="BookComponentAppendix-Usingexpressionforfilenames">Using expression for filenames</h4><p>In this sample we want to move consumed files to a backup folder using today's date as a sub-folder name:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from(&quot;file://inbox?move=backup/${date:now:yyyyMMdd}/${file:name}&quot;).to(&quot;...&quot;);
 ]]></script>
 </div></div><p>See <a shape="rect" href="file-language.html">File Language</a> for more samples.</p><h3 id="BookComponentAppendix-Avoidingreadingthesamefilemorethanonce(idempotentconsumer)">Avoiding reading the same file more than once (idempotent consumer)</h3><p>Camel supports <a shape="rect" href="idempotent-consumer.html">Idempotent Consumer</a> directly within the component so it will skip already processed files. This feature can be enabled by setting the <code>idempotent=true</code> option.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -5585,94 +5589,31 @@ fromF(&quot;hazelcast:%sfoo&quot;, Hazel
     </div>
 
 <div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHazelcastListenerTime</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Long</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> time of the event in millis <strong><a shape="rect" class="unresolved" href="#">Version 2.8</a></strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHazelcastListenerType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> the map consumer sets here "instancelistener" <strong><a shape="rect" class="unresolved" href="#">Version 2.8</a></stro
 ng> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHazelcastListenerActionn</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type of event - here <strong>added</strong> or <strong>removed</strong>. <strong><a shape="rect" class="unresolved" href="#">Version 2.8</a></strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHazelcastInstanceHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> host name of the instance <strong><a shape="rect" class="unresolved" href="#">Version 2.8</a></strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHazelcastInstancePort</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Integer</code> </p></td><td colspan="1" rowspan=
 "1" class="confluenceTd"><p> port number of the instance <strong><a shape="rect" class="unresolved" href="#">Version 2.8</a></strong> </p></td></tr></tbody></table></div>
-<h2 id="BookComponentAppendix-HDFSComponent">HDFS Component</h2>
-<p><strong>Available as of Camel 2.8</strong></p>
-
-<p>The <strong>hdfs</strong> component enables you to read and write messages from/to an HDFS file system. HDFS is the distributed file system at the heart of <a shape="rect" class="external-link" href="http://hadoop.apache.org">Hadoop</a>.</p>
-
-<p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;dependency&gt;
+<h2 id="BookComponentAppendix-HDFSComponent">HDFS Component</h2><p><strong>Available as of Camel 2.8</strong></p><p>The <strong>hdfs</strong> component enables you to read and write messages from/to an HDFS file system. HDFS is the distributed file system at the heart of <a shape="rect" class="external-link" href="http://hadoop.apache.org">Hadoop</a>.</p><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-hdfs&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div>
-
-<h3 id="BookComponentAppendix-URIformat.24">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-hdfs://hostname[:port][/path][?options]
+</div></div><h3 id="BookComponentAppendix-URIformat.24">URI format</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[hdfs://hostname[:port][/path][?options]
 ]]></script>
-</div></div>
-
-<p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code><br clear="none">
-The path is treated in the following way:</p>
-<ol><li>as a consumer, if it's a file, it just reads the file, otherwise if it represents a directory it scans all the file under the path satisfying the configured pattern. All the files under that directory must be of the same type.</li><li>as a producer, if at least one split strategy is defined, the path is considered a directory and under that directory the producer creates a different file per split named using the configured <a shape="rect" href="uuidgenerator.html">uuidgenerator</a>.</li></ol>
-
-
-<h3 id="BookComponentAppendix-Options.18">Options</h3>
-<div class="confluenceTableSmall">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>overwrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The file can be overwritten </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>append</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Append to existing file. Notice that not all HDFS file systems support the append option. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <c
 ode>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The buffer size used by HDFS  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>replication</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>3</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HDFS replication factor  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>blockSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>67108864</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The size of the HDFS blocks  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>fileType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NORMAL_FILE</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be SEQUENCE_FILE, MAP_FILE, ARRAY_FILE, or BLOOMMAP_FILE, see Hadoop </p></td></tr><tr><td colspan="1" rows
 pan="1" class="confluenceTd"><p> <code>fileSystemType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>HDFS</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be LOCAL for local filesystem  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NULL</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>valueType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>TEXT</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>splitStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluence
 Td"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A string describing the strategy on how to split the file based on different criteria. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>openedSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>opened</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When a file is opened for reading/writing the file is renamed with this suffix to avoid to read it during the writing phase. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>readSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>read</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Once the file has been read is renamed with this suffix to avoid to read it again.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>initialDelay</code> </p></td><td colspan="1" rowspan="1" cl
 ass="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> For the consumer, how much to wait (milliseconds) before to start scanning the directory.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>delay</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The interval (milliseconds) between the directory scans. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>pattern</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>*</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The pattern used for scanning the directory  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>chunkSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When rea
 ding a normal file, this is split into chunks producing a message per chunk. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectOnStartup</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9.3/2.10.1:</strong> Whether to connect to the HDFS file system on starting the producer/consumer. If <code>false</code> then the connection is created on-demand. Notice that HDFS may take up till 15 minutes to establish a connection, as it has hardcoded 45 x 20 sec redelivery. By setting this option to <code>false</code> allows your application to startup, and not block for up till 15 minutes. </p></td></tr></tbody></table>
-</div>
-
-<h4 id="BookComponentAppendix-KeyTypeandValueType">KeyType and ValueType</h4>
-<ul><li>NULL it means that the key or the value is absent</li><li>BYTE for writing a byte, the java Byte class is mapped into a BYTE</li><li>BYTES for writing a sequence of bytes. It maps the java ByteBuffer class</li><li>INT for writing java integer</li><li>FLOAT for writing java float</li><li>LONG for writing java long</li><li>DOUBLE for writing java double</li><li>TEXT for writing java strings</li></ul>
-
-
-<p>BYTES is also used with everything else, for example, in Camel a file is sent around as an InputStream, int this case is written in a sequence file or a map file as a sequence of bytes.</p>
-
-<h3 id="BookComponentAppendix-SplittingStrategy">Splitting Strategy</h3>
-<p>In the current version of Hadoop opening a file in append mode is disabled since it's not very reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p>
-<ul><li>If the split strategy option has been defined, the hdfs path will be used as a directory and files will be created using the configured <a shape="rect" href="uuidgenerator.html">uuidgenerator</a></li><li>Every time a splitting condition is met, a new file is created.<br clear="none">
-The splitStrategy option is defined as a string with the following syntax:<br clear="none">
-splitStrategy=&lt;ST&gt;:&lt;value&gt;,&lt;ST&gt;:&lt;value&gt;,*</li></ul>
-
-
-<p>where &lt;ST&gt; can be:</p>
-<ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than &lt;value&gt;</li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than &lt;value&gt;</li><li>IDLE a new file is created, and the old is closed when no writing happened in the last &lt;value&gt; milliseconds</li></ul>
-
-
-    <div class="aui-message warning shadowed information-macro">
+</div></div><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code><br clear="none"> The path is treated in the following way:</p><ol><li>as a consumer, if it's a file, it just reads the file, otherwise if it represents a directory it scans all the file under the path satisfying the configured pattern. All the files under that directory must be of the same type.</li><li>as a producer, if at least one split strategy is defined, the path is considered a directory and under that directory the producer creates a different file per split named using the configured <a shape="rect" href="uuidgenerator.html">UuidGenerator</a>.</li></ol><h3 id="BookComponentAppendix-Options.18">Options</h3><div class="confluenceTableSmall">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>overwrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The file can be overwritten </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>append</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Append to existing file. Notice that not all HDFS file systems support the append option. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <c
 ode>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The buffer size used by HDFS  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>replication</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>3</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HDFS replication factor  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>blockSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>67108864</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The size of the HDFS blocks  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>fileType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NORMAL_FILE</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be SEQUENCE_FILE, MAP_FILE, ARRAY_FILE, or BLOOMMAP_FILE, see Hadoop </p></td></tr><tr><td colspan="1" rows
 pan="1" class="confluenceTd"><p> <code>fileSystemType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>HDFS</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be LOCAL for local filesystem  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NULL</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>valueType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>TEXT</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>splitStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluence
 Td"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A string describing the strategy on how to split the file based on different criteria. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>openedSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>opened</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When a file is opened for reading/writing the file is renamed with this suffix to avoid to read it during the writing phase. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>readSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>read</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Once the file has been read is renamed with this suffix to avoid to read it again.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>initialDelay</code> </p></td><td colspan="1" rowspan="1" cl
 ass="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> For the consumer, how much to wait (milliseconds) before to start scanning the directory.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>delay</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The interval (milliseconds) between the directory scans. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>pattern</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>*</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The pattern used for scanning the directory  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>chunkSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When rea
 ding a normal file, this is split into chunks producing a message per chunk. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectOnStartup</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9.3/2.10.1:</strong> Whether to connect to the HDFS file system on starting the producer/consumer. If <code>false</code> then the connection is created on-demand. Notice that HDFS may take up till 15 minutes to establish a connection, as it has hardcoded 45 x 20 sec redelivery. By setting this option to <code>false</code> allows your application to startup, and not block for up till 15 minutes. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>owner</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.13/2.12.4:</strong> The file
  owner must match this owner for the consumer to pickup the file. Otherwise the file is skipped. </p></td></tr></tbody></table>
+</div><h4 id="BookComponentAppendix-KeyTypeandValueType">KeyType and ValueType</h4><ul><li>NULL it means that the key or the value is absent</li><li>BYTE for writing a byte, the java Byte class is mapped into a BYTE</li><li>BYTES for writing a sequence of bytes. It maps the java ByteBuffer class</li><li>INT for writing java integer</li><li>FLOAT for writing java float</li><li>LONG for writing java long</li><li>DOUBLE for writing java double</li><li>TEXT for writing java strings</li></ul><p>BYTES is also used with everything else, for example, in Camel a file is sent around as an InputStream, int this case is written in a sequence file or a map file as a sequence of bytes.</p><h3 id="BookComponentAppendix-SplittingStrategy">Splitting Strategy</h3><p>In the current version of Hadoop opening a file in append mode is disabled since it's not very reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p><ul><
 li>If the split strategy option has been defined, the hdfs path will be used as a directory and files will be created using the configured <a shape="rect" href="uuidgenerator.html">UuidGenerator</a></li><li>Every time a splitting condition is met, a new file is created.<br clear="none"> The splitStrategy option is defined as a string with the following syntax:<br clear="none"> splitStrategy=&lt;ST&gt;:&lt;value&gt;,&lt;ST&gt;:&lt;value&gt;,*</li></ul><p>where &lt;ST&gt; can be:</p><ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than &lt;value&gt;</li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than &lt;value&gt;</li><li>IDLE a new file is created, and the old is closed when no writing happened in the last &lt;value&gt; milliseconds</li></ul>    <div class="aui-message warning shadowed information-macro">
                             <span class="aui-icon icon-warning">Icon</span>
                 <div class="message-content">
-                            
-<p>note that this strategy currently requires either setting an IDLE value or setting the HdfsConstants.HDFS_CLOSE header to false to use the BYTES/MESSAGES configuration...otherwise, the file will be closed with each message</p>
+                            <p>note that this strategy currently requires either setting an IDLE value or setting the HdfsConstants.HDFS_CLOSE header to false to use the BYTES/MESSAGES configuration...otherwise, the file will be closed with each message</p>
                     </div>
     </div>
-
-
-<p>for example:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-hdfs://localhost/tmp/simple-file?splitStrategy=IDLE:1000,BYTES:5
+<p>for example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[hdfs://localhost/tmp/simple-file?splitStrategy=IDLE:1000,BYTES:5
 ]]></script>
-</div></div>
-<p>it means: a new file is created either when it has been idle for more than 1 second or if more than 5 bytes have been written. So, running <code>hadoop fs -ls /tmp/simple-file</code> you'll see that multiple files have been created.</p>
-
-<h3 id="BookComponentAppendix-MessageHeaders.4">Message Headers</h3>
-
-<p>The following headers are supported by this component:</p>
-
-<h4 id="BookComponentAppendix-Produceronly">Producer only</h4>
-<div class="confluenceTableSmall">
+</div></div><p>it means: a new file is created either when it has been idle for more than 1 second or if more than 5 bytes have been written. So, running <code>hadoop fs -ls /tmp/simple-file</code> you'll see that multiple files have been created.</p><h3 id="BookComponentAppendix-MessageHeaders.4">Message Headers</h3><p>The following headers are supported by this component:</p><h4 id="BookComponentAppendix-Produceronly">Producer only</h4><div class="confluenceTableSmall">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Header </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelFileName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.13:</strong> Specifies the name of the file to write (relative to the endpoint path). The name can be a <code>String</code> or an <a shape="rect" href="expression.html" title="Expression">Expression</a> object. Only relevant when not using a split strategy. </p></td></tr></tbody></table>
-</div>
-
-<h3 id="BookComponentAppendix-Controllingtoclosefilestream">Controlling to close file stream</h3>
-<p><strong>Available as of Camel 2.10.4</strong></p>
-
-<p>When using the <a shape="rect" href="hdfs.html">HDFS</a> producer <strong>without</strong> a split strategy, then the file output stream is by default closed after the write. However you may want to keep the stream open, and only explicitly close the stream later. For that you can use the header <code>HdfsConstants.HDFS_CLOSE</code> (value = <code>"CamelHdfsClose"</code>) to control this. Setting this value to a boolean allows you to explicit control whether the stream should be closed or not.</p>
-
-<p>Notice this does not apply if you use a split strategy, as there are various strategies that can control when the stream is closed.</p>
-
-
-<h3 id="BookComponentAppendix-UsingthiscomponentinOSGi">Using this component in OSGi</h3>
-<p>This component is fully functional in an OSGi environment, however, it requires some actions from the user. Hadoop uses the thread context class loader in order to load resources. Usually, the thread context classloader will be the bundle class loader of the bundle that contains the routes. So, the default configuration files need to be visible from the bundle class loader. A typical way to deal with it is to keep a copy of core-default.xml in your bundle root. That file can be found in the hadoop-common.jar.</p>
+</div><h3 id="BookComponentAppendix-Controllingtoclosefilestream">Controlling to close file stream</h3><p><strong>Available as of Camel 2.10.4</strong></p><p>When using the <a shape="rect" href="hdfs.html">HDFS</a> producer <strong>without</strong> a split strategy, then the file output stream is by default closed after the write. However you may want to keep the stream open, and only explicitly close the stream later. For that you can use the header <code>HdfsConstants.HDFS_CLOSE</code> (value = <code>"CamelHdfsClose"</code>) to control this. Setting this value to a boolean allows you to explicit control whether the stream should be closed or not.</p><p>Notice this does not apply if you use a split strategy, as there are various strategies that can control when the stream is closed.</p><h3 id="BookComponentAppendix-UsingthiscomponentinOSGi">Using this component in OSGi</h3><p>This component is fully functional in an OSGi environment, however, it requires some actions from the user.
  Hadoop uses the thread context class loader in order to load resources. Usually, the thread context classloader will be the bundle class loader of the bundle that contains the routes. So, the default configuration files need to be visible from the bundle class loader. A typical way to deal with it is to keep a copy of core-default.xml in your bundle root. That file can be found in the hadoop-common.jar.</p>
 <h2 id="BookComponentAppendix-HibernateComponent">Hibernate Component</h2>
 
 <p>The <strong>hibernate:</strong> component allows you to work with databases using Hibernate as the object relational mapping technology to map POJOs to database tables. The <strong>camel-hibernate</strong> library is provided by the <a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">Camel Extra</a> project which hosts all *GPL related components for Camel.</p>
@@ -7378,118 +7319,50 @@ from(&quot;timer://foo?period=60000&quot
 <h3 id="BookComponentAppendix-SeeAlso.29">See Also</h3>
 <ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul>
 <ul class="alternate"><li><a shape="rect" href="sql.html">SQL</a></li></ul>
-<h2 id="BookComponentAppendix-JettyComponent">Jetty Component</h2>
-
-<p>The <strong>jetty</strong> component provides HTTP-based <a shape="rect" href="endpoint.html">endpoints</a> for consuming and producing HTTP requests. That is, the Jetty component behaves as a simple Web server.<br clear="none">
-Jetty can also be used as a http client which mean you can also use it with Camel as a producer.</p>
-
-    <div class="aui-message hint shadowed information-macro">
+<h2 id="BookComponentAppendix-JettyComponent">Jetty Component</h2><p>The <strong>jetty</strong> component provides HTTP-based <a shape="rect" href="endpoint.html">endpoints</a> for consuming and producing HTTP requests. That is, the Jetty component behaves as a simple Web server.<br clear="none"> Jetty can also be used as a http client which mean you can also use it with Camel as a producer.</p>    <div class="aui-message hint shadowed information-macro">
                     <p class="title">Stream</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">
-                            
-<p>Jetty is stream based, which means the input it receives is submitted to Camel as a stream. That means you will only be able to read the content of the stream <strong>once</strong>.<br clear="none">
-If you find a situation where the message body appears to be empty or you need to access the data multiple times (eg: doing multicasting, or redelivery error handling)<br clear="none">
-you should use <a shape="rect" href="stream-caching.html">Stream Caching</a> or convert the message body to a <code>String</code> which is safe to be re-read multiple times.</p>
+                            <p>Jetty is stream based, which means the input it receives is submitted to Camel as a stream. That means you will only be able to read the content of the stream <strong>once</strong>.<br clear="none"> If you find a situation where the message body appears to be empty or you need to access the data multiple times (eg: doing multicasting, or redelivery error handling)<br clear="none"> you should use <a shape="rect" href="stream-caching.html">Stream caching</a> or convert the message body to a <code>String</code> which is safe to be re-read multiple times.</p>
                     </div>
     </div>
-
-
-<p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;dependency&gt;
+<p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-jetty&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div>
-
-<h3 id="BookComponentAppendix-URIformat.33">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-jetty:http://hostname[:port][/resourceUri][?options]
+</div></div><h3 id="BookComponentAppendix-URIformat.33">URI format</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[jetty:http://hostname[:port][/resourceUri][?options]
 ]]></script>
-</div></div>
-
-<p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p>
-
-<h3 id="BookComponentAppendix-Options.25">Options</h3>
-<div class="confluenceTableSmall">
+</div></div><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p><h3 id="BookComponentAppendix-Options.25">Options</h3><div class="confluenceTableSmall">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sessionSupport</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether to enable the session manager on the server side of Jetty. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClient.XXX</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 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 <code>httpClien
 t.idleTimeout=30000</code> sets the idle timeout to 30 seconds. And <code>httpClient.timeout=30000</code> sets the request timeout to 30 seconds, in case you want to timeout sooner if you have long running request/response calls. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClient</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a shared <code>org.eclipse.jetty.client.HttpClient</code> for all producers created by this endpoint. This option should only be used in special circumstances. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientMinThreads</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong>: To set a value for minimum number of threads in <code>H
 ttpClient</code> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. If not set it default to min 8 threads used in Jettys thread pool. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientMaxThreads</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong>: To set a value for maximum number of threads in <code>HttpClient</code> thread pool. This setting override any setting configured on component level. Notice that both a min and max size must be configured. If not set it default to max 254 threads used in Jettys thread pool. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpBindingRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td cols
 pan="1" rowspan="1" class="confluenceTd"><p> Reference to an <code>org.apache.camel.component.http.HttpBinding</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <code>HttpBinding</code> can be used to customize how a response should be written for the consumer. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>jettyHttpBindingRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6.0+:</strong> Reference to an <code>org.apache.camel.component.jetty.JettyHttpBinding</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <code>JettyHttpBinding</code> can be used to customize how a response should be written for the producer. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>matchOnUriPrefix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <co
 de>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Whether or not the <code>CamelServlet</code> 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>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>handlers</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies a comma-delimited set of <code>org.mortbay.jetty.Handler</code> instances in your <a shape="rect" href="registry.html" title="Registry">Registry</a> (such as your Spring <code>ApplicationContext</code>). These handlers are added to the Jetty servlet context (for example, to add security). <strong>Important:</strong> You can not use different handlers with different Jetty endpoint
 s using the same port number. The handlers is associated to the port number. If you need different handlers, then use different port numbers. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>chunked</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.2:</strong> If this option is false Jetty servlet will disable the HTTP streaming and set the content-length header on the response </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>enableJmx</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> 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. </p></td></tr><tr><td col
 span="1" rowspan="1" class="confluenceTd"><p> <code>disableStreamCache</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> 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 <code>true</code> 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 <code>false</code> 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. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>throwExceptionOnFailure</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Option to disable throwing the <code>HttpOperationFailedException</code> in case of failed responses from the remote server. This allows you to get all responses regardles of the HTTP status code. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transferException</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:</strong>  If enabled and an <a shape="rect" href="exchange.html" title="Exc
 hange">Exchange</a> failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a <code>application/x-java-serialized-object</code> content type. On the producer side the exception will be deserialized and thrown as is, instead of the <code>HttpOperationFailedException</code>. The caused exception is required to be serialized. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bridgeEndpoint</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.1:</strong> 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 <strong>throwExceptionOnFailure</strong> to be false to let the HttpProducer send all the fault response back. <br clear="none" class="atl-forced-newline">
-<strong>Camel 2.3:</strong> If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". Also consider setting <strong>disableStreamCache</strong> to true to optimize when bridging. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>enableMultipartFilter</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5:</strong> Whether Jetty <code>org.eclipse.jetty.servlets.MultiPartFilter</code> is enabled or not. You should set this value to <code>false</code> when bridging endpoints, to ensure multipart requests is proxied/bridged as well. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>multipartFilterRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:
 </strong> Allows using a custom multipart filter. Note: setting <code>multipartFilterRef</code> forces the value of <code>enableMultipartFilter</code> to <code>true</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>filtersRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9:</strong> 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></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>continuationTimeout</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:</strong> Allows to set a timeout in millis when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> as consumer (server). By default Je
 tty uses 30000. You can use a value of <code>&lt;= 0</code> 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>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>useContinuation</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:</strong> 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. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslContextParametersRef</code><br clear="none" clas
 s="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code><br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> Reference to a <code>org.apache.camel.util.jsse.SSLContextParameters</code> 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>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>traceEnabled</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether to enable HTTP TRACE for this Jetty consumer. By default TRACE is turned off. </p></td></tr><tr><td colspan="1" rowspan="1" clas
 s="confluenceTd"><p> <code>headerFilterStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> Reference to a instance of <code>org.apache.camel.spi.HeaderFilterStrategy</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. It will be used to apply the custom headerFilterStrategy on the new create HttpJettyEndpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>urlRewrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> Refers to a custom <code>org.apache.camel.component.http.UrlRewrite</code> which allows you to rewrite urls when you bridge/proxy endpoints. See more details at <a shape="rect" href="urlrewrite.html" title="UrlRewrite">UrlR
 ewrite</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>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>responseBufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12:</strong> To use a custom buffer size on the <code>javax.servlet.ServletResponse</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> The http proxy Host url which will be used by Jetty client. </p></td></tr><tr><td colspan="1" rowspan="1" cla
 ss="confluenceTd"><p> <code>proxyPort</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> The http proxy port which will be used by Jetty client. </p></td></tr></tbody></table>
-</div>
-
-<h3 id="BookComponentAppendix-MessageHeaders.9">Message Headers</h3>
-
-<p>Camel uses the same message headers as the <a shape="rect" href="http.html">HTTP</a> component.<br clear="none">
-From Camel 2.2, it also uses (Exchange.HTTP_CHUNKED,CamelHttpChunked) header to turn on or turn off the chuched encoding on the camel-jetty consumer.</p>
-
-<p>Camel also populates <strong>all</strong> request.parameter and request.headers. For example, given a client request with the URL, <code><a shape="rect" class="external-link" href="http://myserver/myserver?orderid=123" rel="nofollow">http://myserver/myserver?orderid=123</a></code>, the exchange will contain a header named <code>orderid</code> with the value 123. </p>
-
-<p>Starting with Camel 2.2.0, you can get the request.parameter from the message header not only from Get Method, but also other HTTP method.</p>
-
-<h3 id="BookComponentAppendix-Usage.3">Usage</h3>
-
-<p>The Jetty component supports both consumer and producer endpoints. Another option for producing to other HTTP endpoints, is to use the <a shape="rect" href="http.html">HTTP Component</a></p>
-
-<h3 id="BookComponentAppendix-ComponentOptions">Component Options</h3>
-
-<p>The <code>JettyHttpComponent</code> provides the following options:</p>
-<div class="confluenceTableSmall">
+<strong>Camel 2.3:</strong> If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". Also consider setting <strong>disableStreamCache</strong> to true to optimize when bridging. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>enableMultipartFilter</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5:</strong> Whether Jetty <code>org.eclipse.jetty.servlets.MultiPartFilter</code> is enabled or not. You should set this value to <code>false</code> when bridging endpoints, to ensure multipart requests is proxied/bridged as well. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>multipartFilterRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:
 </strong> Allows using a custom multipart filter. Note: setting <code>multipartFilterRef</code> forces the value of <code>enableMultipartFilter</code> to <code>true</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>filtersRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9:</strong> 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></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>continuationTimeout</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:</strong> Allows to set a timeout in millis when using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> as consumer (server). By default Je
 tty uses 30000. You can use a value of <code>&lt;= 0</code> 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>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>useContinuation</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.6:</strong> 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. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslContextParametersRef</code><br clear="none" clas
 s="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code><br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> Reference to a <code>org.apache.camel.util.jsse.SSLContextParameters</code> 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>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>traceEnabled</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether to enable HTTP TRACE for this Jetty consumer. By default TRACE is turned off. </p></td></tr><tr><td colspan="1" rowspan="1" clas
 s="confluenceTd"><p> <code>headerFilterStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> Reference to a instance of <code>org.apache.camel.spi.HeaderFilterStrategy</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. It will be used to apply the custom headerFilterStrategy on the new create HttpJettyEndpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>urlRewrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> Refers to a custom <code>org.apache.camel.component.http.UrlRewrite</code> which allows you to rewrite urls when you bridge/proxy endpoints. See more details at <a shape="rect" href="urlrewrite.html" title="UrlRewrite">UrlR
 ewrite</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>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>responseBufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12:</strong> To use a custom buffer size on the <code>javax.servlet.ServletResponse</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> The http proxy Host url which will be used by Jetty client. </p></td></tr><tr><td colspan="1" rowspan="1" cla
 ss="confluenceTd"><p> <code>proxyPort</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> The http proxy port which will be used by Jetty client. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> {{sendServerVersion</p></td><th colspan="1" rowspan="1" class="confluenceTh"><p>&#160;</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.13:</strong> if the option is true, jetty will send the server header with the jetty version information to the client which sends the request. </p></td></tr></tbody></table>
+</div><h3 id="BookComponentAppendix-MessageHeaders.9">Message Headers</h3><p>Camel uses the same message headers as the <a shape="rect" href="http.html">HTTP</a> component.<br clear="none"> From Camel 2.2, it also uses (Exchange.HTTP_CHUNKED,CamelHttpChunked) header to turn on or turn off the chuched encoding on the camel-jetty consumer.</p><p>Camel also populates <strong>all</strong> request.parameter and request.headers. For example, given a client request with the URL, <code><a shape="rect" class="external-link" href="http://myserver/myserver?orderid=123" rel="nofollow">http://myserver/myserver?orderid=123</a></code>, the exchange will contain a header named <code>orderid</code> with the value 123.</p><p>Starting with Camel 2.2.0, you can get the request.parameter from the message header not only from Get Method, but also other HTTP method.</p><h3 id="BookComponentAppendix-Usage.3">Usage</h3><p>The Jetty component supports both consumer and producer endpoints. Another option for 
 producing to other HTTP endpoints, is to use the <a shape="rect" href="http.html">HTTP Component</a></p><h3 id="BookComponentAppendix-ComponentOptions">Component Options</h3><p>The <code>JettyHttpComponent</code> provides the following options:</p><div class="confluenceTableSmall">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>enableJmx</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> 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. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslKeyPassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Consumer only</strong>: The password for the keyst
 ore when using SSL. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslPassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Consumer only</strong>: The password when using SSL. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslKeystore</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Consumer only</strong>: The path to the keystore. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>minThreads</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5</strong> <strong>Consumer only</strong>: To set a value for minimum number of threads in server thread pool. Notice that both a
  min and max size must be configured. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>maxThreads</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5</strong> <strong>Consumer only</strong>: To set a value for maximum number of threads in server thread pool. Notice that both a min and max size must be configured. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>threadPool</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5</strong> <strong>Consumer only</strong>: To use a custom thread pool for the server. This option should only be used in special circumstances. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslSocketConnectors</code> </p></td><td colspan="1" rowspan="1" 
 class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3</strong> <strong>Consumer only:</strong> A map which contains per port number specific SSL connectors. See section <em>SSL support</em> for more details. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>socketConnectors</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5</strong> <strong>Consumer only:</strong> A map which contains per port number specific HTTP connectors. Uses the same principle as <code>sslSocketConnectors</code> and therefore see section <em>SSL support</em> for more details. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslSocketConnectorProperties</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" 
 class="confluenceTd"><p> <strong>Camel 2.5</strong> <strong>Consumer only</strong>. A map which contains general SSL connector properties. See section <em>SSL support</em> for more details. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>socketConnectorProperties</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5</strong> <strong>Consumer only</strong>. A map which contains general HTTP connector properties. Uses the same principle as <code>sslSocketConnectorProperties</code> and therefore see section <em>SSL support</em> for more details. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClient</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Deprecated:</strong> <strong>Producer only</strong>: To use a
  custom <code>HttpClient</code> with the jetty producer. This option is removed from Camel 2.11 onwards, instead you can set the option on the endpoint instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientMinThreads</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Producer only</strong>: To set a value for minimum number of threads in <code>HttpClient</code> thread pool. Notice that both a min and max size must be configured. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientMaxThreads</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Producer only</strong>: To set a value for maximum number of threads in <code>HttpClient</code> thread pool. Notice that both a min and max size must be configur
 ed. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientThreadPool</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Deprecated:</strong> <strong>Producer only</strong>: To use a custom thread pool for the client. This option is removed from Camel 2.11 onwards. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslContextParameters</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> To configure a custom SSL/TLS configuration options at the component level.&#160; See&#160; <a shape="rect" href="#BookComponentAppendix-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a> for more details. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>requestBuff
 erSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.2:</strong> Allows to configure a custom value of the request buffer size on the Jetty connectors. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>requestHeaderSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.2:</strong> Allows to configure a custom value of the request header size on the Jetty connectors. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>responseBufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.2:</strong> Allows to configure a custom value of the response buffer size on the Jetty connector
 s. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>responseHeaderSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.2:</strong> Allows to configure a custom value of the response header size on the Jetty connectors. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12.2/2.11.3</strong> To use a http proxy. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyPort</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12.2/2.11.3:</strong> To use a http proxy. </p></td></tr></tbody></table>
-</div>
-
-<h3 id="BookComponentAppendix-ProducerExample">Producer Example</h3>
-
-<p>The following is a basic example of how to send an HTTP request to an existing HTTP endpoint.</p>
-
-<p>in Java DSL</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-from(&quot;direct:start&quot;).to(&quot;jetty://http://www.google.com&quot;);
+</div><h3 id="BookComponentAppendix-ProducerExample">Producer Example</h3><p>The following is a basic example of how to send an HTTP request to an existing HTTP endpoint.</p><p>in Java DSL</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from(&quot;direct:start&quot;).to(&quot;jetty://http://www.google.com&quot;);
 ]]></script>
-</div></div>
-
-<p>or in Spring XML</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;route&gt;
+</div></div><p>or in Spring XML</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
     &lt;to uri=&quot;jetty://http://www.google.com&quot;/&gt;
 &lt;route&gt;
 ]]></script>
-</div></div>
-
-<h3 id="BookComponentAppendix-ConsumerExample">Consumer Example</h3>
-
-<p>In this sample we define a route that exposes a HTTP service at <code><a shape="rect" class="external-link" href="http://localhost:8080/myapp/myservice" rel="nofollow">http://localhost:8080/myapp/myservice</a></code>:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookComponentAppendix-ConsumerExample">Consumer Example</h3><p>In this sample we define a route that exposes a HTTP service at <code><a shape="rect" class="external-link" href="http://localhost:8080/myapp/myservice" rel="nofollow">http://localhost:8080/myapp/myservice</a></code>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;jetty:http://localhost:{{port}}/myapp/myservice&quot;).process(new MyBookService());
 ]]></script>
-</div></div>
-
-    <div class="aui-message warning shadowed information-macro">
+</div></div>    <div class="aui-message warning shadowed information-macro">
                     <p class="title">Usage of localhost</p>
                             <span class="aui-icon icon-warning">Icon</span>
                 <div class="message-content">
-                            
-<p>When you specify <code>localhost</code> in a URL, Camel exposes the endpoint only on the local TCP/IP network interface, so it cannot be accessed from outside the machine it operates on.</p>
-
-<p>If you need to expose a Jetty endpoint on a specific network interface, the numerical IP address of this interface should be used as the host. If you need to expose a Jetty endpoint on all network interfaces, the <code>0.0.0.0</code> address should be used.</p>
+                            <p>When you specify <code>localhost</code> in a URL, Camel exposes the endpoint only on the local TCP/IP network interface, so it cannot be accessed from outside the machine it operates on.</p><p>If you need to expose a Jetty endpoint on a specific network interface, the numerical IP address of this interface should be used as the host. If you need to expose a Jetty endpoint on all network interfaces, the <code>0.0.0.0</code> address should be used.</p>
                     </div>
     </div>
-
-
-<p>Our business logic is implemented in the <code>MyBookService</code> class, which accesses the HTTP request contents and then returns a response.<br clear="none">
-<strong>Note:</strong> The <code>assert</code> call appears in this example, because the code is part of an unit test.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<p>Our business logic is implemented in the <code>MyBookService</code> class, which accesses the HTTP request contents and then returns a response.<br clear="none"> <strong>Note:</strong> The <code>assert</code> call appears in this example, because the code is part of an unit test.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 public class MyBookService implements Processor {
     public void process(Exchange exchange) throws Exception {
@@ -7508,10 +7381,7 @@ public class MyBookService implements Pr
     }
 }
 ]]></script>
-</div></div>
-
-<p>The following sample shows a content-based route that routes all requests containing the URI parameter, <code>one</code>, to the endpoint, <code>mock:one</code>, and all others to <code>mock:other</code>.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>The following sample shows a content-based route that routes all requests containing the URI parameter, <code>one</code>, to the endpoint, <code>mock:one</code>, and all others to <code>mock:other</code>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;jetty:&quot; + serverUri)
     .choice()
@@ -7519,52 +7389,23 @@ from(&quot;jetty:&quot; + serverUri)
     .otherwise()
     .to(&quot;mock:other&quot;);
 ]]></script>
-</div></div>
-<p>So if a client sends the HTTP request, <code><a shape="rect" class="external-link" href="http://serverUri?one=hello" rel="nofollow">http://serverUri?one=hello</a></code>, the Jetty component will copy the HTTP request parameter, <code>one</code> to the exchange's <code>in.header</code>. We can then use the <code>simple</code> language to route exchanges that contain this header to a specific endpoint and all others to another. If we used a language more powerful than <a shape="rect" href="simple.html">Simple</a>--<span style="text-decoration: line-through;">such as</span> <span style="text-decoration: line-through;"><a shape="rect" href="el.html">El</a></span> <span style="text-decoration: line-through;">or</span> <span style="text-decoration: line-through;"><a shape="rect" href="ognl.html">OGNL</a></span>--we could also test for the parameter value and do routing based on the header value as well.</p>
-
-<h3 id="BookComponentAppendix-SessionSupport">Session Support</h3>
-
-<p>The session support option, <code>sessionSupport</code>, can be used to enable a <code>HttpSession</code> object and access the session object while processing the exchange. For example, the following route enables sessions:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;route&gt;
+</div></div><p>So if a client sends the HTTP request, <code><a shape="rect" class="external-link" href="http://serverUri?one=hello" rel="nofollow">http://serverUri?one=hello</a></code>, the Jetty component will copy the HTTP request parameter, <code>one</code> to the exchange's <code>in.header</code>. We can then use the <code>simple</code> language to route exchanges that contain this header to a specific endpoint and all others to another. If we used a language more powerful than <a shape="rect" href="simple.html">Simple</a>--<span style="text-decoration: line-through;">such as</span> <span style="text-decoration: line-through;"><a shape="rect" href="el.html">EL</a></span> <span style="text-decoration: line-through;">or</span> <span style="text-decoration: line-through;"><a shape="rect" href="ognl.html">OGNL</a></span>--we could also test for the parameter value and do routing based on the header value as well.</p><h3 id="BookComponentAppendix-SessionSupport">Session Support</h3><
 p>The session support option, <code>sessionSupport</code>, can be used to enable a <code>HttpSession</code> object and access the session object while processing the exchange. For example, the following route enables sessions:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;route&gt;
     &lt;from uri=&quot;jetty:http://0.0.0.0/myapp/myservice/?sessionSupport=true&quot;/&gt;
     &lt;processRef ref=&quot;myCode&quot;/&gt;
 &lt;route&gt;
 ]]></script>
-</div></div>
-
-<p>The <code>myCode</code> <a shape="rect" href="processor.html">Processor</a> can be instantiated by a Spring <code>bean</code> element:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;bean id=&quot;myCode&quot;class=&quot;com.mycompany.MyCodeProcessor&quot;/&gt;
+</div></div><p>The <code>myCode</code> <a shape="rect" href="processor.html">Processor</a> can be instantiated by a Spring <code>bean</code> element:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;bean id=&quot;myCode&quot;class=&quot;com.mycompany.MyCodeProcessor&quot;/&gt;
 ]]></script>
-</div></div>
-
-<p>Where the processor implementation can access the <code>HttpSession</code> as follows:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-public void process(Exchange exchange) throws Exception {
+</div></div><p>Where the processor implementation can access the <code>HttpSession</code> as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[public void process(Exchange exchange) throws Exception {
     HttpSession session = exchange.getIn(HttpMessage.class).getRequest().getSession();
     ...
 }
 ]]></script>
-</div></div>
-
-<h3 id="BookComponentAppendix-SSLSupport(HTTPS)">SSL Support (HTTPS)</h3>
-
-
-<h5 id="BookComponentAppendix-UsingtheJSSEConfigurationUtility.3">Using the JSSE Configuration Utility</h5>
-
-<p>As of Camel 2.8, the Jetty component supports SSL/TLS configuration through the <a shape="rect" href="camel-configuration-utilities.html">Camel JSSE Configuration Utility</a>.&#160;  This utility greatly decreases the amount of component specific code  you need to write and is configurable at the endpoint and component  levels.&#160; The following examples demonstrate how to use the utility with  the Jetty component.</p>
-
-<h6 id="BookComponentAppendix-Programmaticconfigurationofthecomponent.1">Programmatic configuration of the component</h6>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-KeyStoreParameters ksp = new KeyStoreParameters();
+</div></div><h3 id="BookComponentAppendix-SSLSupport(HTTPS)">SSL Support (HTTPS)</h3><h5 id="BookComponentAppendix-UsingtheJSSEConfigurationUtility.3">Using the JSSE Configuration Utility</h5><p>As of Camel 2.8, the Jetty component supports SSL/TLS configuration through the <a shape="rect" href="camel-configuration-utilities.html">Camel JSSE Configuration Utility</a>.&#160; This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels.&#160; The following examples demonstrate how to use the utility with the Jetty component.</p><h6 id="BookComponentAppendix-Programmaticconfigurationofthecomponent.1">Programmatic configuration of the component</h6><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[KeyStoreParameters ksp = new KeyStoreParameters();
 ksp.setResource(&quot;/users/home/server/keystore.jks&quot;);
 ksp.setPassword(&quot;keystorePassword&quot;);
 
@@ -7578,12 +7419,8 @@ scp.setKeyManagers(kmp);
 JettyComponent jettyComponent = getContext().getComponent(&quot;jetty&quot;, JettyComponent.class);
 jettyComponent.setSslContextParameters(scp);
 ]]></script>
-</div></div>
-
-<h6 id="BookComponentAppendix-SpringDSLbasedconfigurationofendpoint.2">Spring DSL based configuration of endpoint</h6>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-...
+</div></div><h6 id="BookComponentAppendix-SpringDSLbasedconfigurationofendpoint.2">Spring DSL based configuration of endpoint</h6><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[...
   &lt;camel:sslContextParameters
       id=&quot;sslContextParameters&quot;&gt;
     &lt;camel:keyManagers
@@ -7597,39 +7434,11 @@ jettyComponent.setSslContextParameters(s
   &lt;to uri=&quot;jetty:https://127.0.0.1/mail/?sslContextParametersRef=sslContextParameters&quot;/&gt;
 ...
 ]]></script>
-</div></div>
-
-<h5 id="BookComponentAppendix-ConfiguringJettyDirectly">Configuring Jetty Directly</h5>
-
-<p>Jetty provides SSL support out of the box. To enable Jetty to run in SSL mode, simply format the URI with the <code>https://</code> prefix---for example:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;from uri=&quot;jetty:https://0.0.0.0/myapp/myservice/&quot;/&gt;
+</div></div><h5 id="BookComponentAppendix-ConfiguringJettyDirectly">Configuring Jetty Directly</h5><p>Jetty provides SSL support out of the box. To enable Jetty to run in SSL mode, simply format the URI with the <code>https://</code> prefix---for example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;from uri=&quot;jetty:https://0.0.0.0/myapp/myservice/&quot;/&gt;
 ]]></script>
-</div></div>
-
-<p>Jetty also needs to know where to load your keystore from and what passwords to use in order to load the correct SSL certificate. Set the following JVM System Properties:</p>
-
-<p><strong>until Camel 2.2</strong></p>
-<ul><li><code>jetty.ssl.keystore</code> specifies the location of the Java keystore file, which contains the Jetty server's own X.509 certificate in a <em>key entry</em>. A key entry stores the X.509 certificate (effectively, the <em>public key</em>) and also its associated private key.</li><li><code>jetty.ssl.password</code> the store password, which is required to access the keystore file (this is the same password that is supplied to the <code>keystore</code> command's <code>-storepass</code> option).</li><li><code>jetty.ssl.keypassword</code> the key password, which is used to access the certificate's key entry in the keystore (this is the same password that is supplied to the <code>keystore</code> command's <code>-keypass</code> option).</li></ul>
-
-
-<p><strong>from Camel 2.3 onwards</strong></p>
-<ul><li><code>org.eclipse.jetty.ssl.keystore</code> specifies the location of the Java keystore file, which contains the Jetty server's own X.509 certificate in a <em>key entry</em>. A key entry stores the X.509 certificate (effectively, the <em>public key</em>) and also its associated private key.</li><li><code>org.eclipse.jetty.ssl.password</code> the store password, which is required to access the keystore file (this is the same password that is supplied to the <code>keystore</code> command's <code>-storepass</code> option).</li><li><code>org.eclipse.jetty.ssl.keypassword</code> the key password, which is used to access the certificate's key entry in the keystore (this is the same password that is supplied to the <code>keystore</code> command's <code>-keypass</code> option).</li></ul>
-
-
-<p>For details of how to configure SSL on a Jetty endpoint, read the following documentation at the Jetty Site: <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/How+to+configure+SSL" rel="nofollow">http://docs.codehaus.org/display/JETTY/How+to+configure+SSL</a></p>
-
-
-
-
-<p>Some SSL properties aren't exposed directly by Camel, however Camel does expose the underlying SslSocketConnector, which will allow you to set properties like needClientAuth for mutual authentication requiring a client certificate or wantClientAuth for mutual authentication where a client doesn't need a certificate but can have one. There's a slight difference between the various Camel versions:</p>
-
-<p><strong>Up to Camel 2.2</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;bean id=&quot;jetty&quot; class=&quot;org.apache.camel.component.jetty.JettyHttpComponent&quot;&gt;

[... 1245 lines stripped ...]


Mime
View raw message