Author: buildbot
Date: Wed Jul 29 07:21:36 2015
New Revision: 959979

Log:
Production update by buildbot for camel

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

Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Wed Jul 29 
07:21:36 2015
@@ -1268,11 +1268,11 @@ template.send("direct:alias-verify&
 ]]></script>
 </div></div><p></p><h3 id="BookComponentAppendix-SeeAlso.8">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><li><a 
shape="rect" href="crypto.html">Crypto</a> Crypto is also available as a <a 
shape="rect" href="data-format.html">Data Format</a></li></ul> <h2 
id="BookComponentAppendix-CXFComponent">CXF Component</h2><div 
class="confluence-information-macro confluence-information-macro-note"><span 
class="aui-icon aui-icon-small aui-iconfont-warning 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>When using CXF as a consumer, the 
<a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows 
you to factor out how message payloads are received from their processing as a 
RESTful or SOAP web service. This has the potential of using a multitude of 
transports to cons
 ume web services. The bean component's configuration is also simpler and 
provides the fastest method to implement web services using Camel and 
CXF.</p></div></div><div class="confluence-information-macro 
confluence-information-macro-tip"><span class="aui-icon aui-icon-small 
aui-iconfont-approve confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>When using CXF in streaming modes 
(see DataFormat option), then also read about <a shape="rect" 
href="stream-caching.html">Stream caching</a>.</p></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.rbtoc1438085921888 {padding: 0px;}
-div.rbtoc1438085921888 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1438085921888 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1438154333682 {padding: 0px;}
+div.rbtoc1438154333682 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1438154333682 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1438085921888">
+/*]]>*/</style></p><div class="toc-macro rbtoc1438154333682">
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookComponentAppendix-CXFComponent">CXF Component</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookComponentAppendix-URIformat">URI format</a></li><li><a shape="rect" 
href="#BookComponentAppendix-Options">Options</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookComponentAppendix-Thedescriptionsofthedataformats">The descriptions 
of the dataformats</a>
@@ -10962,7 +10962,7 @@ validator:someLocalOrRemoteResource
 </div></div><h3 id="BookComponentAppendix-URIformat.72">URI format</h3><div 
class="code panel pdl" style="border-width: 1px;"><div class="codeContent 
panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[velocity:templateName[?options]
 ]]></script>
-</div></div><p>Where <strong>templateName</strong> is the classpath-local URI 
of the template to invoke; or the complete URL of the remote template (eg: <a 
shape="rect" class="external-link" href="file://folder/myfile.vm" 
rel="nofollow">file://folder/myfile.vm</a>).</p><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.57">Options</h3><div 
class="confluenceTableSmall"><div class="table-wrap"><table 
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"><p>Option</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>loaderCache</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Velocity based file
  loader cache.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Cache for the resource content when it is 
loaded. <br clear="none" class="atl-forced-newline"> Note : as of Camel 2.9 
cached resource content can be cleared via JMX using the endpoint's 
<code>clearContentCache</code> operation.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>encoding</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Character encoding of the 
resource content.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>propertiesFile</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>New option in
  Camel 2.1: The URI of the properties file which is used for VelocityEngine 
initialization.</p></td></tr></tbody></table></div></div><h3 
id="BookComponentAppendix-MessageHeaders.19">Message Headers</h3><p>The 
velocity component sets a couple headers on the message (you can't set these 
yourself and from Camel 2.1 velocity component will not set these headers which 
will cause some side effect on the dynamic template support):</p><div 
class="confluenceTableSmall"><div class="table-wrap"><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>CamelVelocityResourceUri</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The 
<strong>templateName</strong> as a <code>String</code> 
object.</p></td></tr></tbody></table></div></div><p>Headers set during the 
Velocity evaluation are returned t
 o the message and added as headers. Then its kinda possible to return values 
from Velocity to the Message.</p><p>For example, to set the header value of 
<code>fruit</code> in the Velocity template <code>.tm</code>:</p><div 
class="code panel pdl" style="border-width: 1px;"><div class="codeContent 
panelContent pdl">
+</div></div><p>Where <strong>templateName</strong> is the classpath-local URI 
of the template to invoke; or the complete URL of the remote template (eg: <a 
shape="rect" class="external-link" href="file://folder/myfile.vm" 
rel="nofollow">file://folder/myfile.vm</a>).</p><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.57">Options</h3><div 
class="confluenceTableSmall"><div class="table-wrap"><table 
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"><p>Option</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>loaderCache</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Velocity based file
  loader cache.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Cache for the resource content when it is 
loaded. <br clear="none" class="atl-forced-newline"> Note : as of Camel 2.9 
cached resource content can be cleared via JMX using the endpoint's 
<code>clearContentCache</code> operation.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>encoding</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Character encoding of the 
resource content.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>propertiesFile</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>New option in
  Camel 2.1: The URI of the properties file which is used for VelocityEngine 
initialization.</p></td></tr></tbody></table></div></div><h3 
id="BookComponentAppendix-MessageHeaders.19">Message Headers</h3><p>The 
velocity component sets a couple headers on the message (you can't set these 
yourself and from Camel 2.1 velocity component will not set these headers which 
will cause some side effect on the dynamic template support):</p><div 
class="confluenceTableSmall"><div class="table-wrap"><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>CamelVelocityResourceUri</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The 
<strong>templateName</strong> as a <code>String</code> 
object.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><code>CamelVelocitySupplementalCont
 ext</code></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.16:</strong> To add additional 
information to the used VelocityContext. The value of this header should be a 
<code>Map</code> with key/values that will added (override any existing key 
with the same name).<br clear="none">This can be used to pre setup some common 
key/values you want to reuse in your velocity 
endpoints.</p></td></tr></tbody></table></div></div><p>Headers set during the 
Velocity evaluation are returned to the message and added as headers. Then its 
kinda possible to return values from Velocity to the Message.</p><p>For 
example, to set the header value of <code>fruit</code> in the Velocity template 
<code>.tm</code>:</p><div class="code panel pdl" style="border-width: 
1px;"><div class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[$in.setHeader(&quot;fruit&quot;, 
&quot;Apple&quot;)
 ]]></script>
 </div></div><p>The <code>fruit</code> header is now accessible from the 
<code>message.out.headers</code>.</p><h3 
id="BookComponentAppendix-VelocityContext">Velocity Context</h3><p>Camel will 
provide exchange information in the Velocity context (just a <code>Map</code>). 
The <code>Exchange</code> is transfered as:</p><div 
class="confluenceTableSmall"><div class="table-wrap"><table 
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"><p>key</p></th><th colspan="1" rowspan="1" 
class="confluenceTh"><p>value</p></th></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>exchange</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The <code>Exchange</code> 
itself.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>exchange.properties</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The <code>Exchange</code> 
properties.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><co
 de>headers</code></p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>The headers of the In message.</p></td></tr><tr><td 
colspan="1" rowspan="1" 
class="confluenceTd"><p><code>camelContext</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The Camel Context 
instance.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>request</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The In message.</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>in</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The In 
message.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>body</code></p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>The In message body.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>out</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The Out message (only for InOut message 
exchange pattern).</p></
 td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>response</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The Out message (only for InOut message 
exchange pattern).</p></td></tr></tbody></table></div></div><p>Since 
Camel-2.14, you can setup a custom Velocity Context yourself by setting the 
message header <strong>CamelVelocityContext&#160;</strong>just like 
this</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
@@ -11037,7 +11037,7 @@ protected RouteBuilder createRouteBuilde
     };
 }
 ]]></script>
-</div></div><p></p><h3 id="BookComponentAppendix-SeeAlso.67">See Also</h3>
+</div></div><h3 id="BookComponentAppendix-SeeAlso.67">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> <h2 
id="BookComponentAppendix-VMComponent">VM Component</h2>
 
 <p>The <strong>vm:</strong> component provides asynchronous <a shape="rect" 
class="external-link" href="http://www.eecs.harvard.edu/~mdw/proj/seda/"; 
rel="nofollow">SEDA</a> behavior, exchanging messages on a <a shape="rect" 
class="external-link" 
href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/BlockingQueue.html";
 rel="nofollow">BlockingQueue</a> and invoking consumers in a separate thread 
pool.</p>

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Wed Jul 29 07:21:36 
2015
@@ -3685,11 +3685,11 @@ The tutorial has been designed in two pa
 While not actual tutorials you might find working through the source of the 
various <a shape="rect" href="examples.html">Examples</a> useful.</li></ul>
 
 <h2 id="BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring 
Remoting with JMS</h2><p>&#160;</p><div class="confluence-information-macro 
confluence-information-macro-information"><p class="title">Thanks</p><span 
class="aui-icon aui-icon-small aui-iconfont-info 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>This tutorial was kindly donated 
to Apache Camel by Martin Gilday.</p></div></div><h2 
id="BookInOnePage-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.rbtoc1438085952692 {padding: 0px;}
-div.rbtoc1438085952692 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1438085952692 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1438154362531 {padding: 0px;}
+div.rbtoc1438154362531 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1438154362531 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1438085952692">
+/*]]>*/</style></p><div class="toc-macro rbtoc1438154362531">
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring 
Remoting with JMS</a></li><li><a shape="rect" 
href="#BookInOnePage-Preface">Preface</a></li><li><a shape="rect" 
href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect" 
href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect" 
href="#BookInOnePage-About">About</a></li><li><a shape="rect" 
href="#BookInOnePage-CreatetheCamelProject">Create the Camel Project</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookInOnePage-UpdatethePOMwithDependencies">Update the POM with 
Dependencies</a></li></ul>
 </li><li><a shape="rect" href="#BookInOnePage-WritingtheServer">Writing the 
Server</a>
@@ -5789,11 +5789,11 @@ So we completed the last piece in the pi
 <p>This example has been removed from <strong>Camel 2.9</strong> onwards. 
Apache Axis 1.4 is a very old and unsupported framework. We encourage users to 
use <a shape="rect" href="cxf.html">CXF</a> instead of Axis.</p></div></div>
 
 <style type="text/css">/*<![CDATA[*/
-div.rbtoc1438085953076 {padding: 0px;}
-div.rbtoc1438085953076 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1438085953076 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1438154362775 {padding: 0px;}
+div.rbtoc1438154362775 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1438154362775 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style><div class="toc-macro rbtoc1438085953076">
+/*]]>*/</style><div class="toc-macro rbtoc1438154362775">
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookInOnePage-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis 
1.4 with Apache Camel</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect" 
href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect" 
href="#BookInOnePage-Introduction">Introduction</a></li><li><a shape="rect" 
href="#BookInOnePage-SettinguptheprojecttorunAxis">Setting up the project to 
run Axis</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookInOnePage-Maven2">Maven 2</a></li><li><a shape="rect" 
href="#BookInOnePage-wsdl">wsdl</a></li><li><a shape="rect" 
href="#BookInOnePage-ConfiguringAxis">Configuring Axis</a></li><li><a 
shape="rect" href="#BookInOnePage-RunningtheExample">Running the 
Example</a></li></ul>
@@ -17791,11 +17791,11 @@ template.send(&quot;direct:alias-verify&
 ]]></script>
 </div></div><p></p><h3 id="BookInOnePage-SeeAlso.28">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><li><a 
shape="rect" href="crypto.html">Crypto</a> Crypto is also available as a <a 
shape="rect" href="data-format.html">Data Format</a></li></ul> <h2 
id="BookInOnePage-CXFComponent">CXF Component</h2><div 
class="confluence-information-macro confluence-information-macro-note"><span 
class="aui-icon aui-icon-small aui-iconfont-warning 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>When using CXF as a consumer, the 
<a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows 
you to factor out how message payloads are received from their processing as a 
RESTful or SOAP web service. This has the potential of using a multitude of 
transports to consume web 
 services. The bean component's configuration is also simpler and provides the 
fastest method to implement web services using Camel and 
CXF.</p></div></div><div class="confluence-information-macro 
confluence-information-macro-tip"><span class="aui-icon aui-icon-small 
aui-iconfont-approve confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>When using CXF in streaming modes 
(see DataFormat option), then also read about <a shape="rect" 
href="stream-caching.html">Stream caching</a>.</p></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.rbtoc1438085974474 {padding: 0px;}
-div.rbtoc1438085974474 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1438085974474 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1438154382872 {padding: 0px;}
+div.rbtoc1438154382872 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1438154382872 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1438085974474">
+/*]]>*/</style></p><div class="toc-macro rbtoc1438154382872">
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookInOnePage-CXFComponent">CXF Component</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookInOnePage-URIformat">URI format</a></li><li><a shape="rect" 
href="#BookInOnePage-Options">Options</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#BookInOnePage-Thedescriptionsofthedataformats">The descriptions of the 
dataformats</a>
@@ -27485,7 +27485,7 @@ validator:someLocalOrRemoteResource
 </div></div><h3 id="BookInOnePage-URIformat.73">URI format</h3><div 
class="code panel pdl" style="border-width: 1px;"><div class="codeContent 
panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[velocity:templateName[?options]
 ]]></script>
-</div></div><p>Where <strong>templateName</strong> is the classpath-local URI 
of the template to invoke; or the complete URL of the remote template (eg: <a 
shape="rect" class="external-link" href="file://folder/myfile.vm" 
rel="nofollow">file://folder/myfile.vm</a>).</p><p>You can append query options 
to the URI in the following format, 
<code>?option=value&amp;option=value&amp;...</code></p><h3 
id="BookInOnePage-Options.78">Options</h3><div 
class="confluenceTableSmall"><div class="table-wrap"><table 
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"><p>Option</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>loaderCache</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Velocity based file loader 
 cache.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Cache for the resource content when it is 
loaded. <br clear="none" class="atl-forced-newline"> Note : as of Camel 2.9 
cached resource content can be cleared via JMX using the endpoint's 
<code>clearContentCache</code> operation.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>encoding</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Character encoding of the 
resource content.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>propertiesFile</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>New option in Camel 2
 .1: The URI of the properties file which is used for VelocityEngine 
initialization.</p></td></tr></tbody></table></div></div><h3 
id="BookInOnePage-MessageHeaders.19">Message Headers</h3><p>The velocity 
component sets a couple headers on the message (you can't set these yourself 
and from Camel 2.1 velocity component will not set these headers which will 
cause some side effect on the dynamic template support):</p><div 
class="confluenceTableSmall"><div class="table-wrap"><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>CamelVelocityResourceUri</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The 
<strong>templateName</strong> as a <code>String</code> 
object.</p></td></tr></tbody></table></div></div><p>Headers set during the 
Velocity evaluation are returned to the message an
 d added as headers. Then its kinda possible to return values from Velocity to 
the Message.</p><p>For example, to set the header value of <code>fruit</code> 
in the Velocity template <code>.tm</code>:</p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Where <strong>templateName</strong> is the classpath-local URI 
of the template to invoke; or the complete URL of the remote template (eg: <a 
shape="rect" class="external-link" href="file://folder/myfile.vm" 
rel="nofollow">file://folder/myfile.vm</a>).</p><p>You can append query options 
to the URI in the following format, 
<code>?option=value&amp;option=value&amp;...</code></p><h3 
id="BookInOnePage-Options.78">Options</h3><div 
class="confluenceTableSmall"><div class="table-wrap"><table 
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"><p>Option</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>loaderCache</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Velocity based file loader 
 cache.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Cache for the resource content when it is 
loaded. <br clear="none" class="atl-forced-newline"> Note : as of Camel 2.9 
cached resource content can be cleared via JMX using the endpoint's 
<code>clearContentCache</code> operation.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>encoding</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Character encoding of the 
resource content.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>propertiesFile</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>New option in Camel 2
 .1: The URI of the properties file which is used for VelocityEngine 
initialization.</p></td></tr></tbody></table></div></div><h3 
id="BookInOnePage-MessageHeaders.19">Message Headers</h3><p>The velocity 
component sets a couple headers on the message (you can't set these yourself 
and from Camel 2.1 velocity component will not set these headers which will 
cause some side effect on the dynamic template support):</p><div 
class="confluenceTableSmall"><div class="table-wrap"><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>CamelVelocityResourceUri</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The 
<strong>templateName</strong> as a <code>String</code> 
object.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><code>CamelVelocitySupplementalContext</code></td><
 td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 
2.16:</strong> To add additional information to the used VelocityContext. The 
value of this header should be a <code>Map</code> with key/values that will 
added (override any existing key with the same name).<br clear="none">This can 
be used to pre setup some common key/values you want to reuse in your velocity 
endpoints.</p></td></tr></tbody></table></div></div><p>Headers set during the 
Velocity evaluation are returned to the message and added as headers. Then its 
kinda possible to return values from Velocity to the Message.</p><p>For 
example, to set the header value of <code>fruit</code> in the Velocity template 
<code>.tm</code>:</p><div class="code panel pdl" style="border-width: 
1px;"><div class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[$in.setHeader(&quot;fruit&quot;, 
&quot;Apple&quot;)
 ]]></script>
 </div></div><p>The <code>fruit</code> header is now accessible from the 
<code>message.out.headers</code>.</p><h3 
id="BookInOnePage-VelocityContext">Velocity Context</h3><p>Camel will provide 
exchange information in the Velocity context (just a <code>Map</code>). The 
<code>Exchange</code> is transfered as:</p><div 
class="confluenceTableSmall"><div class="table-wrap"><table 
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"><p>key</p></th><th colspan="1" rowspan="1" 
class="confluenceTh"><p>value</p></th></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>exchange</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The <code>Exchange</code> 
itself.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>exchange.properties</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The <code>Exchange</code> 
properties.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>heade
 rs</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The 
headers of the In message.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>camelContext</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The Camel Context 
instance.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>request</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The In message.</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>in</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The In 
message.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>body</code></p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>The In message body.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>out</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The Out message (only for InOut message 
exchange pattern).</p></td></tr>
 <tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>response</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The Out message (only for InOut message 
exchange pattern).</p></td></tr></tbody></table></div></div><p>Since 
Camel-2.14, you can setup a custom Velocity Context yourself by setting the 
message header <strong>CamelVelocityContext&#160;</strong>just like 
this</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
@@ -27560,7 +27560,7 @@ protected RouteBuilder createRouteBuilde
     };
 }
 ]]></script>
-</div></div><p></p><h3 id="BookInOnePage-SeeAlso.87">See Also</h3>
+</div></div><h3 id="BookInOnePage-SeeAlso.87">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> <h2 
id="BookInOnePage-VMComponent">VM Component</h2>
 
 <p>The <strong>vm:</strong> component provides asynchronous <a shape="rect" 
class="external-link" href="http://www.eecs.harvard.edu/~mdw/proj/seda/"; 
rel="nofollow">SEDA</a> behavior, exchanging messages on a <a shape="rect" 
class="external-link" 
href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/BlockingQueue.html";
 rel="nofollow">BlockingQueue</a> and invoking consumers in a separate thread 
pool.</p>

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

Modified: websites/production/camel/content/velocity.html
==============================================================================
--- websites/production/camel/content/velocity.html (original)
+++ websites/production/camel/content/velocity.html Wed Jul 29 07:21:36 2015
@@ -97,7 +97,7 @@
 </div></div><h3 id="Velocity-URIformat">URI format</h3><div class="code panel 
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[velocity:templateName[?options]
 ]]></script>
-</div></div><p>Where <strong>templateName</strong> is the classpath-local URI 
of the template to invoke; or the complete URL of the remote template (eg: <a 
shape="rect" class="external-link" href="file://folder/myfile.vm" 
rel="nofollow">file://folder/myfile.vm</a>).</p><p>You can append query options 
to the URI in the following format, 
<code>?option=value&amp;option=value&amp;...</code></p><h3 
id="Velocity-Options">Options</h3><div class="confluenceTableSmall"><div 
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" 
rowspan="1" class="confluenceTh"><p>Option</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>loaderCache</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Velocity based file loader 
cache.</
 p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Cache for the resource content when it is 
loaded. <br clear="none" class="atl-forced-newline"> Note : as of Camel 2.9 
cached resource content can be cleared via JMX using the endpoint's 
<code>clearContentCache</code> operation.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>encoding</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Character encoding of the 
resource content.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>propertiesFile</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>New option in Camel 2.1: The 
 URI of the properties file which is used for VelocityEngine 
initialization.</p></td></tr></tbody></table></div></div><h3 
id="Velocity-MessageHeaders">Message Headers</h3><p>The velocity component sets 
a couple headers on the message (you can't set these yourself and from Camel 
2.1 velocity component will not set these headers which will cause some side 
effect on the dynamic template support):</p><div 
class="confluenceTableSmall"><div class="table-wrap"><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>CamelVelocityResourceUri</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The 
<strong>templateName</strong> as a <code>String</code> 
object.</p></td></tr></tbody></table></div></div><p>Headers set during the 
Velocity evaluation are returned to the message and added as heade
 rs. Then its kinda possible to return values from Velocity to the 
Message.</p><p>For example, to set the header value of <code>fruit</code> in 
the Velocity template <code>.tm</code>:</p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Where <strong>templateName</strong> is the classpath-local URI 
of the template to invoke; or the complete URL of the remote template (eg: <a 
shape="rect" class="external-link" href="file://folder/myfile.vm" 
rel="nofollow">file://folder/myfile.vm</a>).</p><p>You can append query options 
to the URI in the following format, 
<code>?option=value&amp;option=value&amp;...</code></p><h3 
id="Velocity-Options">Options</h3><div class="confluenceTableSmall"><div 
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" 
rowspan="1" class="confluenceTh"><p>Option</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>loaderCache</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Velocity based file loader 
cache.</
 p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Cache for the resource content when it is 
loaded. <br clear="none" class="atl-forced-newline"> Note : as of Camel 2.9 
cached resource content can be cleared via JMX using the endpoint's 
<code>clearContentCache</code> operation.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>encoding</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Character encoding of the 
resource content.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>propertiesFile</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>New option in Camel 2.1: The 
 URI of the properties file which is used for VelocityEngine 
initialization.</p></td></tr></tbody></table></div></div><h3 
id="Velocity-MessageHeaders">Message Headers</h3><p>The velocity component sets 
a couple headers on the message (you can't set these yourself and from Camel 
2.1 velocity component will not set these headers which will cause some side 
effect on the dynamic template support):</p><div 
class="confluenceTableSmall"><div class="table-wrap"><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>CamelVelocityResourceUri</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The 
<strong>templateName</strong> as a <code>String</code> 
object.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><code>CamelVelocitySupplementalContext</code></td><td 
colspan="1" r
 owspan="1" class="confluenceTd"><p><strong>Camel 2.16:</strong> To add 
additional information to the used VelocityContext. The value of this header 
should be a <code>Map</code> with key/values that will added (override any 
existing key with the same name).<br clear="none">This can be used to pre setup 
some common key/values you want to reuse in your velocity 
endpoints.</p></td></tr></tbody></table></div></div><p>Headers set during the 
Velocity evaluation are returned to the message and added as headers. Then its 
kinda possible to return values from Velocity to the Message.</p><p>For 
example, to set the header value of <code>fruit</code> in the Velocity template 
<code>.tm</code>:</p><div class="code panel pdl" style="border-width: 
1px;"><div class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[$in.setHeader(&quot;fruit&quot;, 
&quot;Apple&quot;)
 ]]></script>
 </div></div><p>The <code>fruit</code> header is now accessible from the 
<code>message.out.headers</code>.</p><h3 id="Velocity-VelocityContext">Velocity 
Context</h3><p>Camel will provide exchange information in the Velocity context 
(just a <code>Map</code>). The <code>Exchange</code> is transfered as:</p><div 
class="confluenceTableSmall"><div class="table-wrap"><table 
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"><p>key</p></th><th colspan="1" rowspan="1" 
class="confluenceTh"><p>value</p></th></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>exchange</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The <code>Exchange</code> 
itself.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>exchange.properties</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The <code>Exchange</code> 
properties.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>headers</c
 ode></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The headers 
of the In message.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>camelContext</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The Camel Context 
instance.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>request</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The In message.</p></td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>in</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>The In 
message.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>body</code></p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>The In message body.</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>out</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The Out message (only for InOut message 
exchange pattern).</p></td></tr><tr><
 td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>response</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>The Out message (only for InOut message 
exchange pattern).</p></td></tr></tbody></table></div></div><p>Since 
Camel-2.14, you can setup a custom Velocity Context yourself by setting the 
message header <strong>CamelVelocityContext&#160;</strong>just like 
this</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
@@ -172,7 +172,7 @@ protected RouteBuilder createRouteBuilde
     };
 }
 ]]></script>
-</div></div><p></p><h3 id="Velocity-SeeAlso">See Also</h3>
+</div></div><h3 id="Velocity-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">


Reply via email to