Modified: websites/production/camel/content/point-to-point-channel.html
==============================================================================
--- websites/production/camel/content/point-to-point-channel.html (original)
+++ websites/production/camel/content/point-to-point-channel.html Thu Sep 11 
10:19:20 2014
@@ -36,6 +36,16 @@
     <![endif]-->
 
 
+  <link href='//camel.apache.org/styles/highlighter/styles/shCoreCamel.css' 
rel='stylesheet' type='text/css' />
+  <link href='//camel.apache.org/styles/highlighter/styles/shThemeCamel.css' 
rel='stylesheet' type='text/css' />
+  <script src='//camel.apache.org/styles/highlighter/scripts/shCore.js' 
type='text/javascript'></script>
+  <script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js' 
type='text/javascript'></script>
+  <script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js' 
type='text/javascript'></script>
+  
+  <script type="text/javascript">
+  SyntaxHighlighter.defaults['toolbar'] = false;
+  SyntaxHighlighter.all();
+  </script>
 
     <title>
     Apache Camel: Point to Point Channel
@@ -75,16 +85,15 @@
        <tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3 
id="PointtoPointChannel-PointtoPointChannel">Point to Point Channel</h3>
-
-<p>Camel supports the <a shape="rect" class="external-link" 
href="http://www.enterpriseintegrationpatterns.com/PointToPointChannel.html"; 
rel="nofollow">Point to Point Channel</a> from the <a shape="rect" 
href="enterprise-integration-patterns.html">EIP patterns</a> using the 
following components</p>
-
-<ul><li><a shape="rect" href="seda.html">Seda</a> for in-VM seda based 
messaging</li><li><a shape="rect" href="jms.html">JMS</a> for working with JMS 
Queues for high performance, clustering and load balancing</li><li><a 
shape="rect" href="jpa.html">JPA</a> for using a database as a simple message 
queue</li><li><a shape="rect" href="xmpp.html">XMPP</a> for point-to-point 
communication over XMPP (Jabber)</li><li>and others</li></ul>
-
-
-<p><img class="confluence-embedded-image confluence-external-resource" 
src="http://www.enterpriseintegrationpatterns.com/img/PointToPointSolution.gif"; 
data-image-src="http://www.enterpriseintegrationpatterns.com/img/PointToPointSolution.gif";></p>
-
-<h4 id="PointtoPointChannel-UsingThisPattern">Using This Pattern</h4>
+<div class="wiki-content maincontent"><h3 
id="PointtoPointChannel-PointtoPointChannel">Point to Point 
Channel</h3><p>Camel supports the <a shape="rect" class="external-link" 
href="http://www.enterpriseintegrationpatterns.com/PointToPointChannel.html"; 
rel="nofollow">Point to Point Channel</a> from the <a shape="rect" 
href="enterprise-integration-patterns.html">EIP patterns</a> using the 
following components</p><ul><li><a shape="rect" href="seda.html">SEDA</a> for 
in-VM seda based messaging</li><li><a shape="rect" href="jms.html">JMS</a> for 
working with JMS Queues for high performance, clustering and load 
balancing</li><li><a shape="rect" href="jpa.html">JPA</a> for using a database 
as a simple message queue</li><li><a shape="rect" href="xmpp.html">XMPP</a> for 
point-to-point communication over XMPP (Jabber)</li><li>and 
others</li></ul><p><img class="confluence-embedded-image 
confluence-external-resource" 
src="http://www.enterpriseintegrationpatterns.com/img/PointToPointSolution.gif";
  
data-image-src="http://www.enterpriseintegrationpatterns.com/img/PointToPointSolution.gif";></p><p>The
 following example demonstrates point to point messaging using the&#160;<a 
shape="rect" href="jms.html">JMS</a>&#160;component&#160;</p><p><strong>Using 
the&#160;<a shape="rect" href="fluent-builders.html">Fluent 
Builders</a></strong></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;jms:queue:foo&quot;);]]></script>
+</div></div><p>&#160;</p><p><strong><strong>Using the&#160;<a shape="rect" 
href="spring-xml-extensions.html">Spring XML 
Extensions</a></strong></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;route&gt;
+       &lt;from uri=&quot;direct:start&quot;/&gt;
+       &lt;to uri=&quot;jms:queue:foo&quot;/&gt;
+&lt;/route&gt;]]></script>
+</div></div><p>&#160;</p><p>&#160;</p><p></p><h4 
id="PointtoPointChannel-UsingThisPattern">Using This Pattern</h4>
 
 <p>If you would like to use this EIP Pattern then please read the <a 
shape="rect" href="getting-started.html">Getting Started</a>, you may also find 
the <a shape="rect" href="architecture.html">Architecture</a> useful 
particularly the description of <a shape="rect" 
href="endpoint.html">Endpoint</a> and <a shape="rect" 
href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" 
href="examples.html">Examples</a> first before trying this pattern 
out.</p></div>
         </td>

Modified: websites/production/camel/content/rabbitmq.html
==============================================================================
--- websites/production/camel/content/rabbitmq.html (original)
+++ websites/production/camel/content/rabbitmq.html Thu Sep 11 10:19:20 2014
@@ -96,7 +96,7 @@
 </div></div><h3 id="RabbitMQ-URIformat">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[rabbitmq://hostname[:port]/exchangeName?[options]
 ]]></script>
-</div></div><p>Where <strong>hostname</strong> is the hostname of the running 
rabbitmq instance or cluster. Port is optional and if not specified then 
defaults to the RabbitMQ client default (5672). The exchange name determines 
which exchange produced messages will sent to. In the case of consumers, the 
exchange name determines which exchange the queue will bind to.</p><h3 
id="RabbitMQ-Options">Options</h3><div class="confluenceTableSmall"><div 
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" 
rowspan="1" class="confluenceTh"><p>Property</p></th><th colspan="1" 
rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" 
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>autoAck</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>If messages should be auto 
acknowledged</p></td></tr><tr><
 td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>autoDelete</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>If it is true, the exchange will be deleted 
when it is no longer in use</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>durable</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>If we are declaring a durable exchange (the 
exchange will survive a server restart)</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>queue</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>random uuid</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The queue to receive messages 
from</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>routingKey</code></p></td><td colspan="1" 
rowspan="1" cla
 ss="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>The routing key to use when binding a consumer queue to 
the exchange. For producer routing keys, you set the header (see header 
section)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>threadPoolSize</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>10</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The consumer uses a Thread Pool Executor 
with a fixed number of threads. This setting allows you to set that number of 
threads.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>username</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>username in case of authenticated 
access</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>password</code></p></td><td colspan="1" 
rowspan="1" cla
 ss="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>password for authenticated access</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>vhost</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>/</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>the vhost for the 
channel</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>exchangeType</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>direct</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><strong>Camel 2.12.2:</strong> The exchange 
type such as direct or topic.</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.12.3:</strong> If the 
bridgeEndpoint is true, the prod
 ucer will ignore the message header of "rabbitmq.EXCHANGE_NAME" and 
"rabbitmq.ROUTING_KEY"</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>addresses</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.3:</strong> If this 
option is set, camel-rabbitmq will try to create connection based on the 
setting of option addresses. The addresses value is a string which looks like 
"server1:12345, server2:12345"</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>connectionTimeout</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Connection 
timeout</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>requestedChannelMax</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="conf
 luenceTd"><p><strong>Camel 2.14:</strong> Connection requested channel max 
(max number of channels offered)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>requestedFrameMax</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Connection requested frame 
max (max size of frame offered)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>requestedHeartbeat</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Connection requested 
heartbeat (heart-beat in seconds offered)</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p>sslProtocol</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Enables SSL on connection, 
accepted value are `true`, `
 TLS` and 'SSLv3`</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>trustManager</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Configure SSL trust 
manager, SSL should be enabled for this option to be 
effective</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>clientProperties</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Connection client 
properties (client info used in negotiating with the 
server)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>connectionFactory</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Custom RabbitMQ connection 
factory. When this option is set, all connection options (connectionTimeou
 t, requestedChannelMax...) set on URI are not used</p></td></tr><tr><td 
colspan="1" rowspan="1" 
class="confluenceTd"><p>automaticRecoveryEnabled</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Enables connection 
automatic recovery (uses connection implementation that performs automatic 
recovery when connection shutdown is not initiated by the 
application)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>networkRecoveryInterval</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>5000</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Network recoverty interval 
in milliseconds (interval used when recovering from network 
failure)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>topologyRecoveryEnabled</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan
 ="1" class="confluenceTd"><p><strong>Camel 2.14:</strong> Enables connection 
topology recovery (should topology recovery be performed?)</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p>prefetchEnabled</p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><strong>Camel 2.14:</strong> Enables the 
quality of service on the RabbitMQConsumer side, you need to specify the option 
of <strong>prefetchSize</strong>, <strong>prefetchCount</strong>, 
<strong>prefetchGlobal</strong> at the same time</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p>prefetchSize</p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><strong>Camel 2.14:</strong> The maximum 
amount of content (measured in octets) that the server will deliver, 0 if 
unlimited.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>prefetchCount</
 p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.14:</strong> 
The maximum number of messages that the server will deliver, 0 if 
unlimited.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>prefetchGlobal</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> If the settings should be 
applied to the entire channel rather than each consumer</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd">declare</td><td colspan="1" 
rowspan="1" class="confluenceTd">true</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.14</strong>: If the option is true, camel 
declare the exchange and queue name and bind them together. If the option is 
false, camel won't declare the exchange and queue name on the 
server.</td></tr></tbody></table></div></div><p>See <a shape="rect"
  class="external-link" 
href="http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html";
 
rel="nofollow">http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html</a>
 and the AMQP specification for more information on connection options.</p><h2 
id="RabbitMQ-Customconnectionfactory">Custom connection factory</h2><div 
class="code panel pdl" style="border-width: 1px;"><div class="codeContent 
panelContent pdl">
+</div></div><p>Where <strong>hostname</strong> is the hostname of the running 
rabbitmq instance or cluster. Port is optional and if not specified then 
defaults to the RabbitMQ client default (5672). The exchange name determines 
which exchange produced messages will sent to. In the case of consumers, the 
exchange name determines which exchange the queue will bind to.</p><h3 
id="RabbitMQ-Options">Options</h3><div class="confluenceTableSmall"><div 
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" 
rowspan="1" class="confluenceTh"><p>Property</p></th><th colspan="1" 
rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" 
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>autoAck</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>If messages should be auto 
acknowledged</p></td></tr><tr><
 td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>autoDelete</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>If it is true, the exchange will be deleted 
when it is no longer in use</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>durable</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>If we are declaring a durable exchange (the 
exchange will survive a server restart)</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>queue</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>random uuid</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The queue to receive messages 
from</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>routingKey</code></p></td><td colspan="1" 
rowspan="1" cla
 ss="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>The routing key to use when binding a consumer queue to 
the exchange. For producer routing keys, you set the header (see header 
section)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>threadPoolSize</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>10</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The consumer uses a Thread Pool Executor 
with a fixed number of threads. This setting allows you to set that number of 
threads.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>username</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>username in case of authenticated 
access</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>password</code></p></td><td colspan="1" 
rowspan="1" cla
 ss="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>password for authenticated access</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>vhost</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>/</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>the vhost for the 
channel</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>exchangeType</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>direct</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><strong>Camel 2.12.2:</strong> The exchange 
type such as direct or topic.</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.12.3:</strong> If the 
bridgeEndpoint is true, the prod
 ucer will ignore the message header of "rabbitmq.EXCHANGE_NAME" and 
"rabbitmq.ROUTING_KEY"</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>addresses</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.3:</strong> If this 
option is set, camel-rabbitmq will try to create connection based on the 
setting of option addresses. The addresses value is a string which looks like 
"server1:12345, server2:12345"</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>connectionTimeout</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Connection 
timeout</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>requestedChannelMax</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="conf
 luenceTd"><p><strong>Camel 2.14:</strong> Connection requested channel max 
(max number of channels offered)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>requestedFrameMax</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Connection requested frame 
max (max size of frame offered)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>requestedHeartbeat</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Connection requested 
heartbeat (heart-beat in seconds offered)</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p>sslProtocol</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Enables SSL on connection, 
accepted value are `true`, `
 TLS` and 'SSLv3`</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>trustManager</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Configure SSL trust 
manager, SSL should be enabled for this option to be 
effective</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>clientProperties</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Connection client 
properties (client info used in negotiating with the 
server)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>connectionFactory</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Custom RabbitMQ connection 
factory. When this option is set, all connection options (connectionTimeou
 t, requestedChannelMax...) set on URI are not used</p></td></tr><tr><td 
colspan="1" rowspan="1" 
class="confluenceTd"><p>automaticRecoveryEnabled</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Enables connection 
automatic recovery (uses connection implementation that performs automatic 
recovery when connection shutdown is not initiated by the 
application)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>networkRecoveryInterval</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>5000</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> Network recoverty interval 
in milliseconds (interval used when recovering from network 
failure)</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>topologyRecoveryEnabled</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan
 ="1" class="confluenceTd"><p><strong>Camel 2.14:</strong> Enables connection 
topology recovery (should topology recovery be performed?)</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p>prefetchEnabled</p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><strong>Camel 2.14:</strong> Enables the 
quality of service on the RabbitMQConsumer side, you need to specify the option 
of <strong>prefetchSize</strong>, <strong>prefetchCount</strong>, 
<strong>prefetchGlobal</strong> at the same time</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p>prefetchSize</p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><strong>Camel 2.14:</strong> The maximum 
amount of content (measured in octets) that the server will deliver, 0 if 
unlimited.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>prefetchCount</
 p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.14:</strong> 
The maximum number of messages that the server will deliver, 0 if 
unlimited.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>prefetchGlobal</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.14:</strong> If the settings should be 
applied to the entire channel rather than each consumer</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd">declare</td><td colspan="1" 
rowspan="1" class="confluenceTd">true</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.14</strong>: If the option is true, camel 
declare the exchange and queue name and bind them together. If the option is 
false, camel won't declare the exchange and queue name on the 
server.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceT
 d">concurrentConsumers</td><td colspan="1" rowspan="1" 
class="confluenceTd">1</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.14:</strong> Number of concurrent 
consumers when consuming from broker. (eg similar as to the same option for the 
<a shape="rect" href="jms.html">JMS</a> component).</td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd">deadLetterRoutingKey</td><td 
colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" 
rowspan="1" class="confluenceTd"><strong>Camel 2.14:</strong> The routing key 
for the dead letter exchange</td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd">deadLetterExchange</td><td colspan="1" rowspan="1" 
class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.14:</strong> The name of the dead letter 
exchange</td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd">deadLetterExchangeType</td><td colspan="1" rowspan="1" 
class="confluenceTd">direct</td><td c
 olspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.14:</strong> The 
type of the dead letter exchange</td></tr></tbody></table></div></div><p>See <a 
shape="rect" class="external-link" 
href="http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html";
 
rel="nofollow">http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html</a>
 and the AMQP specification for more information on connection options.</p><h2 
id="RabbitMQ-Customconnectionfactory">Custom connection factory</h2><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;customConnectionFactory&quot; 
class=&quot;com.rabbitmq.client.ConnectionFactory&quot;&gt;
 &lt;property name=&quot;host&quot; value=&quot;localhost&quot;/&gt;
 &lt;property name=&quot;port&quot; value=&quot;5672&quot;/&gt;

Modified: websites/production/camel/content/scala-dsl-eip.html
==============================================================================
--- websites/production/camel/content/scala-dsl-eip.html (original)
+++ websites/production/camel/content/scala-dsl-eip.html Thu Sep 11 10:19:20 
2014
@@ -100,11 +100,11 @@ You can check the <a shape="rect" class=
 
 
 <style type="text/css">/*<![CDATA[*/
-div.rbtoc1407575871104 {padding: 0px;}
-div.rbtoc1407575871104 ul {list-style: none;margin-left: 0px;}
-div.rbtoc1407575871104 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1410430661820 {padding: 0px;}
+div.rbtoc1410430661820 ul {list-style: none;margin-left: 0px;}
+div.rbtoc1410430661820 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style><div class="toc-macro rbtoc1407575871104">
+/*]]>*/</style><div class="toc-macro rbtoc1410430661820">
 <ul class="toc-indentation"><li><span class="TOCOutline">1</span> <a 
shape="rect" href="#ScalaDSL-EIP-Messagingsystems">Messaging systems</a>
 <ul class="toc-indentation"><li><span class="TOCOutline">1.1</span> <a 
shape="rect" href="#ScalaDSL-EIP-Pipelinepipeline">Pipeline</a></li><li><span 
class="TOCOutline">1.2</span> <a shape="rect" 
href="#ScalaDSL-EIP-Filterfilter">Filter</a></li></ul>
 </li><li><span class="TOCOutline">2</span> <a shape="rect" 
href="#ScalaDSL-EIP-Messagingchannels">Messaging channels</a>

Modified: websites/production/camel/content/siteindex.html
==============================================================================
--- websites/production/camel/content/siteindex.html (original)
+++ websites/production/camel/content/siteindex.html Thu Sep 11 10:19:20 2014
@@ -91,7 +91,7 @@
 
 <p>
 <table class="grid" width="99%" cellspacing="0"><tr><td colspan="2" 
rowspan="1">
-         <table width="100%"><tr><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-0-9">0-9</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-A">A</a> ... 31</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-B">B</a> ... 40</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-C">C</a> ... 157</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-D">D</a> ... 31</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-E">E</a> ... 29</td></tr><tr><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-F">F</a> ... 14</td><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-G">G</a> ... 26</td><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-H">H</a> ... 84</td><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-I">I</a> ... 17</td><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-J">J</a> ... 27</td><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-K">K</a> ... 3</td></tr><tr><td colspan="1" row
 span="1"><a shape="rect" href="#index-L">L</a> ... 18</td><td colspan="1" 
rowspan="1"><a shape="rect" href="#index-M">M</a> ... 32</td><td colspan="1" 
rowspan="1"><a shape="rect" href="#index-N">N</a> ... 9</td><td colspan="1" 
rowspan="1"><a shape="rect" href="#index-O">O</a> ... 6</td><td colspan="1" 
rowspan="1"><a shape="rect" href="#index-P">P</a> ... 24</td><td colspan="1" 
rowspan="1"><a shape="rect" href="#index-Q">Q</a> ... 5</td></tr><tr><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-R">R</a> ... 32</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-S">S</a> ... 78</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-T">T</a> ... 42</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-U">U</a> ... 17</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-V">V</a> ... 8</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-W">W</a> ... 
30</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-X">X</a> ... 14</td><
 td colspan="1" rowspan="1"><a shape="rect" href="#index-Y">Y</a> ... 1</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-Z">Z</a> ... 4</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-%21@%23%24">!@#$</a> ... 
0</td><td colspan="1" rowspan="1">&#160;</td><td colspan="1" 
rowspan="1">&#160;</td></tr></table>
+         <table width="100%"><tr><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-0-9">0-9</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-A">A</a> ... 31</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-B">B</a> ... 40</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-C">C</a> ... 157</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-D">D</a> ... 31</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-E">E</a> ... 29</td></tr><tr><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-F">F</a> ... 14</td><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-G">G</a> ... 27</td><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-H">H</a> ... 84</td><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-I">I</a> ... 17</td><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-J">J</a> ... 27</td><td colspan="1" rowspan="1"><a 
shape="rect" href="#index-K">K</a> ... 4</td></tr><tr><td colspan="1" row
 span="1"><a shape="rect" href="#index-L">L</a> ... 18</td><td colspan="1" 
rowspan="1"><a shape="rect" href="#index-M">M</a> ... 33</td><td colspan="1" 
rowspan="1"><a shape="rect" href="#index-N">N</a> ... 11</td><td colspan="1" 
rowspan="1"><a shape="rect" href="#index-O">O</a> ... 7</td><td colspan="1" 
rowspan="1"><a shape="rect" href="#index-P">P</a> ... 24</td><td colspan="1" 
rowspan="1"><a shape="rect" href="#index-Q">Q</a> ... 5</td></tr><tr><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-R">R</a> ... 32</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-S">S</a> ... 79</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-T">T</a> ... 42</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-U">U</a> ... 17</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-V">V</a> ... 8</td><td 
colspan="1" rowspan="1"><a shape="rect" href="#index-W">W</a> ... 
30</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-X">X</a> ... 14</td>
 <td colspan="1" rowspan="1"><a shape="rect" href="#index-Y">Y</a> ... 
1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Z">Z</a> ... 
4</td><td colspan="1" rowspan="1"><a shape="rect" 
href="#index-%21@%23%24">!@#$</a> ... 0</td><td colspan="1" 
rowspan="1">&#160;</td><td colspan="1" rowspan="1">&#160;</td></tr></table>
         </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 
style="margin-top: 0px"><a shape="rect" name="index-0-9"></a>0-9</h4>
         </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a 
shape="rect" name="index-A"></a>A</h4>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="acknowledgment.html">Acknowledgment</a>
@@ -434,7 +434,7 @@
              <div class="smalltext" style="margin: 0 0 0 36px">Camel 2.13.2 
release New and Noteworthy Welcome to the 2.13.2 release which is mainly a bug 
fix release with 41 issues resolved.. For more details see the&#160;JIRA 
tickets Known Issues See&#160;Camel 2.13.0 Release Important changes to 
consider when upgrading See&#160;</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="camel-2140-release.html">Camel 2.14.0 Release</a>
         <br clear="none">
-             <div class="smalltext" style="margin: 0 0 0 36px">Camel 2.14.0 
release (currently in progress) New and Noteworthy Welcome to the 2.14.0 
release which approx XXX issues resolved (new features, improvements and bug 
fixes such as...) Support for running on Java 1.8 JVMs Spring 4.x supported. 
REST DSL to def</div>
+             <div class="smalltext" style="margin: 0 0 0 36px">Camel 2.14.0 
release (currently in progress) &#160; New and Noteworthy Welcome to the 2.14.0 
release which approx XXX issues resolved (new features, improvements and bug 
fixes such as...) Support for running on Java 1.8 JVMs Spring 4.x supported. 
REST DSL to d</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="camel-220-release.html">Camel 2.2.0 Release</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">Camel 2.2.0 
release New and Noteworthy Welcome to the 2.2.0 release which approx 180 issues 
resolved (new features, improvements and bug fixes such as...) Routing Slip now 
breaks when an exception occurred MINA now supports easier configuration of 
multipl</div>
@@ -1033,6 +1033,9 @@
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="google-summerofcode.html">Google SummerOfCode</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">Ideas for the 
Apache Sponsored GSoC2009. 2009 Full support of the Camel DSL in Ruby and 
Python Camel provides an Enterprise Integration Patterns Domain Specific 
Language which can be used from many languges such as Java, XML, Groovy, Scala. 
There is suppo</div>
+                             <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="googledrive.html">GoogleDrive</a>
+        <br clear="none">
+             <div class="smalltext" style="margin: 0 0 0 36px">GoogleDrive 
Component Available as of Camel 2.14 The Google Drive component provides access 
to the Google Drive file storage service via the Google Drive Web APIs. Google 
Drive uses the&#160;OAuth 2.0 protocol&#160;for authenticating a Google account 
and authorizin</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="gora.html">Gora</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">Camel-Gora is 
an Apache Camel component that allows you to work with NoSQL databases using 
the Apache Gora framework. Available as of Camel 2.14 Maven users will need to 
add the following dependency to their pom.xml for this component: 
&lt;dependency&gt; &#160;&lt;grou</div>
@@ -1472,6 +1475,9 @@
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">JXPath Camel 
supports JXPath to allow XPath expressions to be used on beans in an Expression 
or Predicate to be used in the DSL or Xml Configuration. For example you could 
use JXPath to create an Predicate in a Message Filter or as an Expression for a 
Rec</div>
         </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a 
shape="rect" name="index-K"></a>K</h4>
+                             <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="kafka.html">Kafka</a>
+        <br clear="none">
+             <div class="smalltext" style="margin: 0 0 0 36px">Kafka Component 
Available as of Camel 2.13 The kafka: component is used for communicating with 
Apache Kafka&#160;message broker. Maven users will need to add the following 
dependency to their pom.xml for this component: &lt;dependency&gt; 
&lt;groupId&gt;org.apache.camel&lt;/</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="karaf.html">Karaf</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">Karaf Support 
Apache Camel is designed to work nicely into Apache Karaf OSGi container. It 
includes: Camel features descriptor allowing to easily and quickly install 
Camel in Karaf. Karaf commands allowing you to view, start, stop, get info, 
about the Cam</div>
@@ -1572,7 +1578,7 @@
              <div class="smalltext" style="margin: 0 0 0 36px">Message Bus 
Camel supports the Message Bus from the EIP patterns. You could view Camel as a 
Message Bus itself as it allows producers and consumers to be decoupled. Folks 
often assume that a Message Bus is a JMS though so you may wish to refer to the 
JMS </div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="message-channel.html">Message Channel</a>
         <br clear="none">
-             <div class="smalltext" style="margin: 0 0 0 36px">Message Channel 
Camel supports the Message Channel from the EIP patterns. The Message Channel 
is an internal implementation detail of the Endpoint interface and all 
interactions with the Message Channel are via the Endpoint interfaces. For more 
details se</div>
+             <div class="smalltext" style="margin: 0 0 0 36px">Message Channel 
Camel supports the Message Channel from the EIP patterns. The Message Channel 
is an internal implementation detail of the Endpoint interface and all 
interactions with the Message Channel are via the Endpoint interfaces. Example 
In JMS, Mes</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="message-dispatcher.html">Message Dispatcher</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">Message 
Dispatcher Camel supports the Message Dispatcher from the EIP patterns using 
various approaches. You can use a component like JMS with selectors to 
implement a Selective Consumer as the Message Dispatcher implementation. Or you 
can use an Endpoint</div>
@@ -1597,6 +1603,9 @@
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="messaging-mapper.html">Messaging Mapper</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">Messaging 
Mapper Camel supports the Messaging Mapper from the EIP patterns by using 
either Message Translator pattern or the Type Converter module. See also 
Message Translator Type Converter CXF for JAX-WS support for binding business 
logic to messaging &amp;</div>
+                             <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="metrics-component.html">Metrics Component</a>
+        <br clear="none">
+             <div class="smalltext" style="margin: 0 0 0 36px">Metrics 
Component Available as of Camel 2.14 The&#160;metrics:&#160;component allows to 
collect various metrics directly from Camel routes. Supported metric types 
are&#160;Metrics Component,&#160;Metrics Component, Metrics 
Component&#160;and&#160;Metrics Component.&#160;Metrics&#160;provides si</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="mina.html">MINA</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">MINA Component 
Deprecated This component is deprecated as the Apache Mina 1.x project is EOL. 
Instead use Mina2 or Netty instead. The mina: component is a transport for 
working with Apache MINA Maven users will need to add the following dependency 
to thei</div>
@@ -1649,6 +1658,12 @@
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="netty-http-server-example.html">Netty HTTP Server Example</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">Netty HTTP 
Server Example Available as of Camel 2.12 This example is located in the 
examples/camel-example-netty-http directory of the Camel distribution. There is 
a README.txt file with instructions how to run it. If you use maven then you 
can easily pac</div>
+                             <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="netty4.html">Netty4</a>
+        <br clear="none">
+             <div class="smalltext" style="margin: 0 0 0 36px">Netty Component 
Available as of Camel 2.14 The netty4 component in Camel is a socket 
communication component, based on the Netty project version 4. Netty is a NIO 
client server framework which enables quick and easy development of network 
applications suc</div>
+                             <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="netty4-http.html">Netty4 HTTP</a>
+        <br clear="none">
+             <div class="smalltext" style="margin: 0 0 0 36px">Netty4 HTTP 
Component Available as of Camel 2.14 The netty4-http component is an extension 
to&#160;Netty4 component to facilitiate HTTP transport with Netty4. This camel 
component supports both producer and consumer endpoints. Netty is stream based, 
which mean</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="news.html">News</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">News</div>
@@ -1668,6 +1683,9 @@
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="oldlinks.html">OldLinks</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px"></div>
+                             <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="olingo2.html">Olingo2</a>
+        <br clear="none">
+             <div class="smalltext" style="margin: 0 0 0 36px">Olingo2 
Component Available as of Camel 2.14 The Olingo2 component utilizes&#160;Apache 
Olingo version 2.0&#160;APIs to interact with OData 2.0 and 3.0 compliant 
services. A number of popular commercial and enterprise vendors and products 
support the OData protocol</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="oncompletion.html">OnCompletion</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">OnCompletion 
Camel has this concept of a Unit of Work that encompass the Exchange. The unit 
of work among others supports synchronization callbacks that are invoked when 
the Exchange is complete. The callback API is defined in 
org.apache.camel.spi.Synchro</div>
@@ -1704,7 +1722,7 @@
              <div class="smalltext" style="margin: 0 0 0 36px">Pluggable Class 
Resolvers Available since Camel 2.0 Camel provides pluggable class resolvers 
allowing third party platforms and contains to provide their own resolvers in 
case the default ones does not work on their platform. For example we provide a 
WebS</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="point-to-point-channel.html">Point to Point Channel</a>
         <br clear="none">
-             <div class="smalltext" style="margin: 0 0 0 36px">Point to Point 
Channel Camel supports the Point to Point Channel from the EIP patterns using 
the following components Seda for in-VM seda based messaging JMS for working 
with JMS Queues for high performance, clustering and load balancing JPA for 
using a d</div>
+             <div class="smalltext" style="margin: 0 0 0 36px">Point to Point 
Channel Camel supports the Point to Point Channel from the EIP patterns using 
the following components SEDA for in-VM seda based messaging JMS for working 
with JMS Queues for high performance, clustering and load balancing JPA for 
using a d</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="pojo.html">Pojo</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">Pojo Component 
The pojo: component is now just an alias for the Bean component. Has been 
removed in Camel 2.0.</div>
@@ -2098,9 +2116,12 @@
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="support.html">Support</a>
         <br clear="none">
              <div class="smalltext" style="margin: 0 0 0 36px">Getting Help If 
you are experiencing problems using Camel then please report your problem to 
our Discussion Forums. This allows the entire community to help with your 
problem. If indeed a bug has been identified in the Camel software, then 
document the pr</div>
+                             <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="swagger.html">Swagger</a>
+        <br clear="none">
+             <div class="smalltext" style="margin: 0 0 0 36px">Swagger 
Component Available as of Camel 2.14 The &#160;Rest DSL&#160;can be integrated 
with the&#160;camel-swagger module which is used for exposing the REST services 
and their APIs using Swagger. Maven users will need to add the following 
dependency to their&#160;pom.xml&#160;fo</div>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="syslog.html">Syslog</a>
         <br clear="none">
-             <div class="smalltext" style="margin: 0 0 0 36px">Syslog 
DataFormat Available as of Camel 2.6 The syslog dataformat is used for working 
with RFC3164 messages. This component supports the following: UDP consumption 
of syslog messages Agnostic data format using either plain String objects or 
SyslogMessage </div>
+             <div class="smalltext" style="margin: 0 0 0 36px">Syslog 
DataFormat Available as of Camel 2.6 The syslog dataformat is used for working 
with RFC3164&#160;and RFC5424 messages. This component supports the following: 
UDP consumption of syslog messages Agnostic data format using either plain 
String objects or Sy</div>
         </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 
style="margin-top: 0px"><a shape="rect" name="index-T"></a>T</h4>
                              <span class="icon icon-page" 
title="Page">Page:</span>                 <a shape="rect" 
href="team.html">Team</a>
         <br clear="none">

Modified: websites/production/camel/content/syslog.html
==============================================================================
--- websites/production/camel/content/syslog.html (original)
+++ websites/production/camel/content/syslog.html Thu Sep 11 10:19:20 2014
@@ -84,39 +84,16 @@
        <tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Syslog-SyslogDataFormat">Syslog 
DataFormat</h2>
-<p><strong>Available as of Camel 2.6</strong></p>
-
-<p>The <strong>syslog</strong> dataformat is used for working with <a 
shape="rect" class="external-link" href="http://www.ietf.org/rfc/rfc3164.txt"; 
rel="nofollow">RFC3164</a> messages.</p>
-
-<p>This component supports the following:</p>
-<ul class="alternate"><li>UDP consumption of syslog messages</li><li>Agnostic 
data format using either plain String objects or SyslogMessage model 
objects.</li><li><a shape="rect" href="type-converter.html">Type Converter</a> 
from/to SyslogMessage and String</li><li>Integration with the <a shape="rect" 
href="mina.html">camel-mina</a> component.</li><li>Integration with the <a 
shape="rect" href="netty.html">camel-netty</a> component.</li></ul>
-
-
-<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;
+<div class="wiki-content maincontent"><h2 id="Syslog-SyslogDataFormat">Syslog 
DataFormat</h2><p><strong>Available as of Camel 2.6</strong></p><p>The 
<strong>syslog</strong> dataformat is used for working with <a shape="rect" 
class="external-link" href="http://www.ietf.org/rfc/rfc3164.txt"; 
rel="nofollow">RFC3164</a>&#160;and RFC5424 messages.</p><p>This component 
supports the following:</p><ul class="alternate"><li>UDP consumption of syslog 
messages</li><li>Agnostic data format using either plain String objects or 
SyslogMessage model objects.</li><li><a shape="rect" 
href="type-converter.html">Type Converter</a> from/to SyslogMessage and 
String</li><li>Integration with the <a shape="rect" 
href="mina.html">camel-mina</a> component.</li><li>Integration with the <a 
shape="rect" href="netty.html">camel-netty</a> component.</li><li><strong>Camel 
2.14:</strong> Encoder and decoder for the&#160;<a shape="rect" 
href="netty.html">camel-netty</a>&#160;component.</li><li><strong>Camel 
2.14:</str
 ong>&#160;Support for RFC5424 also.</li></ul><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-syslog&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="Syslog-RFC3164Syslogprotocol">RFC3164 Syslog protocol</h3>
-<p>Syslog uses the user datagram protocol (UDP) <a shape="rect" 
class="unresolved" href="#">1</a> as its underlying transport layer mechanism.  
<br clear="none">
-The UDP port that has been assigned to syslog is 514.</p>
-
-<p>To expose a Syslog listener service we reuse the existing <a shape="rect" 
href="mina.html">camel-mina</a> component or <a shape="rect" 
href="netty.html">camel-netty</a> where we just use the 
<code>Rfc3164SyslogDataFormat</code> to marshal and unmarshal messages</p>
-
-<h4 id="Syslog-ExposingaSysloglistener">Exposing a Syslog listener</h4>
-<p>In our Spring XML file, we configure an endpoint to listen for udp messages 
on port 10514, note that in netty we disable the defaultCodec, this <br 
clear="none">
-will allow a fallback to a NettyTypeConverter and delivers the message as an 
InputStream:</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;camelContext id=&quot;myCamel&quot; 
xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
+</div></div><h3 id="Syslog-RFC3164Syslogprotocol">RFC3164 Syslog 
protocol</h3><p>Syslog uses the user datagram protocol (UDP) <a shape="rect" 
class="unresolved" href="#">1</a> as its underlying transport layer mechanism. 
<br clear="none"> The UDP port that has been assigned to syslog is 
514.</p><p>To expose a Syslog listener service we reuse the existing <a 
shape="rect" href="mina.html">camel-mina</a> component or <a shape="rect" 
href="netty.html">camel-netty</a> where we just use the 
<code>Rfc3164SyslogDataFormat</code> to marshal and unmarshal messages. Notice 
that from&#160;<strong>Camel 2.14</strong> onwards the syslog dataformat is 
renamed to <code>SyslogDataFormat</code>.</p><h3 
id="Syslog-RFC5424Syslogprotocol">RFC5424 Syslog 
protocol</h3><p><strong>Available as of Camel 2.14</strong></p><p>To expose a 
Syslog listener service we reuse the existing&#160;<a shape="rect" 
href="mina.html">camel-mina</a>&#160;component or&#160;<a shape="rect" 
href="netty.html">camel-netty</a>&#160
 ;where we just use the&#160;<code>SyslogDataFormat</code>&#160;to marshal and 
unmarshal messages</p><h4 id="Syslog-ExposingaSysloglistener">Exposing a Syslog 
listener</h4><p>In our Spring XML file, we configure an endpoint to listen for 
udp messages on port 10514, note that in netty we disable the defaultCodec, 
this <br clear="none"> will allow a fallback to a NettyTypeConverter and 
delivers the message as an InputStream:</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;camelContext id=&quot;myCamel&quot; 
xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
 
     &lt;dataFormats&gt;
           &lt;syslog id=&quot;mySyslog&quot;/&gt;
@@ -130,12 +107,8 @@ will allow a fallback to a NettyTypeConv
 
 &lt;/camelContext&gt;
 ]]></script>
-</div></div>
-
-<p>The same route using <a shape="rect" href="mina.html">camel-mina</a></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;camelContext id=&quot;myCamel&quot; 
xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
+</div></div><p>The same route using <a shape="rect" 
href="mina.html">camel-mina</a></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;camelContext id=&quot;myCamel&quot; 
xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
 
     &lt;dataFormats&gt;
           &lt;syslog id=&quot;mySyslog&quot;/&gt;
@@ -149,14 +122,8 @@ will allow a fallback to a NettyTypeConv
 
 &lt;/camelContext&gt;
 ]]></script>
-</div></div>
-
-
-<h4 id="Syslog-Sendingsyslogmessagestoaremotedestination">Sending syslog 
messages to a remote destination</h4>
-
-<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;camelContext id=&quot;myCamel&quot; 
xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
+</div></div><h4 id="Syslog-Sendingsyslogmessagestoaremotedestination">Sending 
syslog messages to a remote destination</h4><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;camelContext id=&quot;myCamel&quot; 
xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
 
     &lt;dataFormats&gt;
         &lt;syslog id=&quot;mySyslog&quot;/&gt;
@@ -170,9 +137,7 @@ will allow a fallback to a NettyTypeConv
 
 &lt;/camelContext&gt;
 ]]></script>
-</div></div>
-
-<h3 id="Syslog-SeeAlso">See Also</h3>
+</div></div><p></p><h3 id="Syslog-SeeAlso">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></div>
         </td>
         <td valign="top">

Modified: websites/production/camel/content/transport.html
==============================================================================
--- websites/production/camel/content/transport.html (original)
+++ websites/production/camel/content/transport.html Thu Sep 11 10:19:20 2014
@@ -250,7 +250,9 @@ disruptor-vm:someName[?&lt;option&gt;]
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used by 
Camel applications outside Google App Engine (GAE) for programmatic login to 
GAE applications. See also <a shape="rect" href="gae.html">Camel Components for 
Google App Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="gtask.html">GTask</a> / <a 
shape="rect" href="gae.html">camel-gae</a></p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[gtask://queue-name[?options]
 ]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports 
asynchronous message processing on Google App Engine by using the <a 
shape="rect" class="external-link" 
href="http://code.google.com/appengine/docs/java/taskqueue/"; 
rel="nofollow">task queueing service</a> as message queue. See also <a 
shape="rect" href="gae.html">Camel Components for Google App 
Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="gmail.html">GMail</a> / <a 
shape="rect" href="gae.html">camel-gae</a></p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports 
asynchronous message processing on Google App Engine by using the <a 
shape="rect" class="external-link" 
href="http://code.google.com/appengine/docs/java/taskqueue/"; 
rel="nofollow">task queueing service</a> as message queue. See also <a 
shape="rect" href="gae.html">Camel Components for Google App 
Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="googledrive.html">Google 
Drive</a> / <a shape="rect" 
href="googledrive.html">camel-google-drive</a></p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[google-drive://endpoint-prefix/endpoint?[options]]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports 
interaction with <a shape="rect" class="external-link" 
href="https://developers.google.com/drive/v2/reference/"; rel="nofollow">Google 
Drive's REST API</a>.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="gmail.html">GMail</a> / <a 
shape="rect" href="gae.html">camel-gae</a></p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[gmail://user@g[oogle]mail.com[?options]
 ]]></script>
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports 
sending of emails via the <a shape="rect" class="external-link" 
href="http://code.google.com/appengine/docs/java/mail/"; rel="nofollow">mail 
service</a> of Google App Engine. See also <a shape="rect" 
href="gae.html">Camel Components for Google App 
Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="gora.html">Gora</a><span>/ 
camel-gora</span></p><div class="code panel pdl" style="border-width: 
1px;"><div class="codeContent panelContent pdl">
@@ -391,7 +393,10 @@ disruptor-vm:someName[?&lt;option&gt;]
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Working 
with TCP and UDP protocols using Java NIO based capabilities offered by the <a 
shape="rect" class="external-link" href="http://netty.io/"; 
rel="nofollow">Netty</a> project</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="netty-http.html">Netty HTTP</a> / 
camel-netty-http</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[netty-http:http:[port]/context-path[?options]
 ]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Netty 
HTTP server and client using the <a shape="rect" class="external-link" 
href="http://netty.io/"; rel="nofollow">Netty</a> project</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" 
href="optaplanner.html">O</a><a shape="rect" href="openshift.html">penshift</a> 
/ camel-openshift</p><div class="code panel pdl" style="border-width: 
1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Netty 
HTTP server and client using the <a shape="rect" class="external-link" 
href="http://netty.io/"; rel="nofollow">Netty</a> project</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" 
href="olingo2.html">Olingo2</a> / camel-olingo2</p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[olingo2:endpoint/resource-path[?options]
+]]></script>
+</div></div></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>Communicates with <a shape="rect" class="external-link" 
href="http://www.odata.org/documentation/odata-version-2-0"; 
rel="nofollow">OData 2.0</a> services using <a shape="rect" 
class="external-link" href="http://olingo.apache.org/";>Apache Olingo</a> 
2.0.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a 
shape="rect" href="optaplanner.html">O</a><a shape="rect" 
href="openshift.html">penshift</a> / camel-openshift</p><div class="code panel 
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[openshift:clientId[?options]
 ]]></script>
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To manage 
your <a shape="rect" class="external-link" href="https://www.openshift.com/"; 
rel="nofollow">Openshift</a> applications.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><a shape="rect" 
href="optaplanner.html">OptaPlanner</a> / camel-optaplanner</p><div class="code 
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">

Modified: websites/production/camel/content/tutorial-jmsremoting.html
==============================================================================
--- websites/production/camel/content/tutorial-jmsremoting.html (original)
+++ websites/production/camel/content/tutorial-jmsremoting.html Thu Sep 11 
10:19:20 2014
@@ -94,11 +94,11 @@
                     </div>
     </div>
 <h2 id="Tutorial-JmsRemoting-Preface">Preface</h2><p>This tutorial aims to 
guide the reader through the stages of creating a project which uses Camel to 
facilitate the routing of messages from a JMS queue to a <a shape="rect" 
class="external-link" href="http://www.springramework.org"; 
rel="nofollow">Spring</a> service. The route works in a synchronous fashion 
returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1407575870636 {padding: 0px;}
-div.rbtoc1407575870636 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1407575870636 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1410430661158 {padding: 0px;}
+div.rbtoc1410430661158 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1410430661158 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1407575870636">
+/*]]>*/</style></p><div class="toc-macro rbtoc1410430661158">
 <ul class="toc-indentation"><li><a shape="rect" 
href="#Tutorial-JmsRemoting-TutorialonSpringRemotingwithJMS">Tutorial on Spring 
Remoting with JMS</a></li><li><a shape="rect" 
href="#Tutorial-JmsRemoting-Preface">Preface</a></li><li><a shape="rect" 
href="#Tutorial-JmsRemoting-Prerequisites">Prerequisites</a></li><li><a 
shape="rect" 
href="#Tutorial-JmsRemoting-Distribution">Distribution</a></li><li><a 
shape="rect" href="#Tutorial-JmsRemoting-About">About</a></li><li><a 
shape="rect" href="#Tutorial-JmsRemoting-CreatetheCamelProject">Create the 
Camel Project</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#Tutorial-JmsRemoting-UpdatethePOMwithDependencies">Update the POM with 
Dependencies</a></li></ul>
 </li><li><a shape="rect" href="#Tutorial-JmsRemoting-WritingtheServer">Writing 
the Server</a>

Modified: websites/production/camel/content/uris.html
==============================================================================
--- websites/production/camel/content/uris.html (original)
+++ websites/production/camel/content/uris.html Thu Sep 11 10:19:20 2014
@@ -255,7 +255,9 @@ disruptor-vm:someName[?&lt;option&gt;]
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used by 
Camel applications outside Google App Engine (GAE) for programmatic login to 
GAE applications. See also <a shape="rect" href="gae.html">Camel Components for 
Google App Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="gtask.html">GTask</a> / <a 
shape="rect" href="gae.html">camel-gae</a></p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[gtask://queue-name[?options]
 ]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports 
asynchronous message processing on Google App Engine by using the <a 
shape="rect" class="external-link" 
href="http://code.google.com/appengine/docs/java/taskqueue/"; 
rel="nofollow">task queueing service</a> as message queue. See also <a 
shape="rect" href="gae.html">Camel Components for Google App 
Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="gmail.html">GMail</a> / <a 
shape="rect" href="gae.html">camel-gae</a></p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports 
asynchronous message processing on Google App Engine by using the <a 
shape="rect" class="external-link" 
href="http://code.google.com/appengine/docs/java/taskqueue/"; 
rel="nofollow">task queueing service</a> as message queue. See also <a 
shape="rect" href="gae.html">Camel Components for Google App 
Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="googledrive.html">Google 
Drive</a> / <a shape="rect" 
href="googledrive.html">camel-google-drive</a></p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[google-drive://endpoint-prefix/endpoint?[options]]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports 
interaction with <a shape="rect" class="external-link" 
href="https://developers.google.com/drive/v2/reference/"; rel="nofollow">Google 
Drive's REST API</a>.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="gmail.html">GMail</a> / <a 
shape="rect" href="gae.html">camel-gae</a></p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[gmail://user@g[oogle]mail.com[?options]
 ]]></script>
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Supports 
sending of emails via the <a shape="rect" class="external-link" 
href="http://code.google.com/appengine/docs/java/mail/"; rel="nofollow">mail 
service</a> of Google App Engine. See also <a shape="rect" 
href="gae.html">Camel Components for Google App 
Engine</a>.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="gora.html">Gora</a><span>/ 
camel-gora</span></p><div class="code panel pdl" style="border-width: 
1px;"><div class="codeContent panelContent pdl">
@@ -396,7 +398,10 @@ disruptor-vm:someName[?&lt;option&gt;]
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Working 
with TCP and UDP protocols using Java NIO based capabilities offered by the <a 
shape="rect" class="external-link" href="http://netty.io/"; 
rel="nofollow">Netty</a> project</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" href="netty-http.html">Netty HTTP</a> / 
camel-netty-http</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[netty-http:http:[port]/context-path[?options]
 ]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Netty 
HTTP server and client using the <a shape="rect" class="external-link" 
href="http://netty.io/"; rel="nofollow">Netty</a> project</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" 
href="optaplanner.html">O</a><a shape="rect" href="openshift.html">penshift</a> 
/ camel-openshift</p><div class="code panel pdl" style="border-width: 
1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Netty 
HTTP server and client using the <a shape="rect" class="external-link" 
href="http://netty.io/"; rel="nofollow">Netty</a> project</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" 
href="olingo2.html">Olingo2</a> / camel-olingo2</p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[olingo2:endpoint/resource-path[?options]
+]]></script>
+</div></div></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>Communicates with <a shape="rect" class="external-link" 
href="http://www.odata.org/documentation/odata-version-2-0"; 
rel="nofollow">OData 2.0</a> services using <a shape="rect" 
class="external-link" href="http://olingo.apache.org/";>Apache Olingo</a> 
2.0.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a 
shape="rect" href="optaplanner.html">O</a><a shape="rect" 
href="openshift.html">penshift</a> / camel-openshift</p><div class="code panel 
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" 
type="syntaxhighlighter"><![CDATA[openshift:clientId[?options]
 ]]></script>
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To manage 
your <a shape="rect" class="external-link" href="https://www.openshift.com/"; 
rel="nofollow">Openshift</a> applications.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><a shape="rect" 
href="optaplanner.html">OptaPlanner</a> / camel-optaplanner</p><div class="code 
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">


Reply via email to