Author: buildbot
Date: Fri Feb 6 06:18:23 2015
New Revision: 939183
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 Fri Feb 6
06:18:23 2015
@@ -1342,11 +1342,11 @@ template.send("direct:alias-verify&
</div>
</div>
<p>The <strong>cxf:</strong> component provides integration with <a
shape="rect" href="http://cxf.apache.org";>Apache CXF</a> for connecting to
JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1422782234926 {padding: 0px;}
-div.rbtoc1422782234926 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1422782234926 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1423203437646 {padding: 0px;}
+div.rbtoc1423203437646 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1423203437646 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1422782234926">
+/*]]>*/</style></p><div class="toc-macro rbtoc1423203437646">
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF
Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI
format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#CXF-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
@@ -12329,22 +12329,14 @@ validator:someLocalOrRemoteResource
</div></div><h3 id="BookComponentAppendix-URIformat.73">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[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&option=value&...</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 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">
+</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&option=value&...</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">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[$in.setHeader('fruit',
'Apple')
]]></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>
<code>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
intance. </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 </strong>just like
this</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</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 </strong>just like
this</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[ VelocityContext velocityContext = new
VelocityContext(variableMap);
exchange.getIn().setHeader("CamelVelocityContext",
velocityContext);
]]></script>
-</div></div><p> </p><h3 id="BookComponentAppendix-Hotreloading.2">Hot
reloading</h3><p>The Velocity template resource is, by default, hot reloadable
for both file and classpath resources (expanded jar). If you set
<code>contentCache=true</code>, Camel will only load the resource once, and
thus hot reloading is not possible. This scenario can be used in production,
when the resource never changes.</p><h3
id="BookComponentAppendix-Dynamictemplates.1">Dynamic
templates</h3><p><strong>Available as of Camel 2.1</strong><br clear="none">
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these headers
is set then Camel uses this over the endpoint configured resource. This allows
you to provide a dynamic template at runtime.</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> Type </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> CamelVelocityResourceUri
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> String
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.1:</strong> A URI for the template resource to use instead of the endpoint
configured. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> CamelVelocityTemplate </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> String </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.1:</strong> The template
to use instead of the endpoint configured. </p></td></tr></tbody></table></div>
-</div><h3 id="BookComponentAppendix-Samples.16">Samples</h3><p>For example you
could use something like</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+</div></div><p> </p><h3 id="BookComponentAppendix-Hotreloading.2">Hot
reloading</h3><p>The Velocity template resource is, by default, hot reloadable
for both file and classpath resources (expanded jar). If you set
<code>contentCache=true</code>, Camel will only load the resource once, and
thus hot reloading is not possible. This scenario can be used in production,
when the resource never changes.</p><h3
id="BookComponentAppendix-Dynamictemplates.1">Dynamic
templates</h3><p><strong>Available as of Camel 2.1</strong><br clear="none">
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these headers
is set then Camel uses this over the endpoint configured resource. This allows
you to provide a dynamic template at runtime.</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 col
span="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p>CamelVelocityResourceUri</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.1:</strong> A URI for the template
resource to use instead of the endpoint configured.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p>CamelVelocityTemplate</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.1:</strong> The template to use instead
of the endpoint configured.</p></td></tr></tbody></table></div></div><h3
id="BookComponentAppendix-Samples.16">Samples</h3><p>For example you could use
something like</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("activemq:My.Queue").
to("velocity:com/acme/MyResponse.vm");
]]></script>
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 Fri Feb 6 06:18:23
2015
@@ -4121,11 +4121,11 @@ While not actual tutorials you might fin
</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.rbtoc1423153135547 {padding: 0px;}
-div.rbtoc1423153135547 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1423153135547 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1423203443676 {padding: 0px;}
+div.rbtoc1423203443676 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1423203443676 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1423153135547">
+/*]]>*/</style></p><div class="toc-macro rbtoc1423203443676">
<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>
@@ -6311,11 +6311,11 @@ So we completed the last piece in the pi
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1423153138210 {padding: 0px;}
-div.rbtoc1423153138210 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1423153138210 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1423203444031 {padding: 0px;}
+div.rbtoc1423203444031 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1423203444031 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1423153138210">
+/*]]>*/</style><div class="toc-macro rbtoc1423203444031">
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-AXIS-Camel-TutorialusingAxis1.4withApacheCamel">Tutorial using
Axis 1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-AXIS-Camel-Prerequisites">Prerequisites</a></li><li><a
shape="rect"
href="#Tutorial-AXIS-Camel-Distribution">Distribution</a></li><li><a
shape="rect"
href="#Tutorial-AXIS-Camel-Introduction">Introduction</a></li><li><a
shape="rect" href="#Tutorial-AXIS-Camel-SettinguptheprojecttorunAxis">Setting
up the project to run Axis</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-AXIS-Camel-Maven2">Maven 2</a></li><li><a shape="rect"
href="#Tutorial-AXIS-Camel-wsdl">wsdl</a></li><li><a shape="rect"
href="#Tutorial-AXIS-Camel-ConfiguringAxis">Configuring Axis</a></li><li><a
shape="rect" href="#Tutorial-AXIS-Camel-RunningtheExample">Running the
Example</a></li></ul>
@@ -18843,11 +18843,11 @@ template.send("direct:alias-verify&
</div>
</div>
<p>The <strong>cxf:</strong> component provides integration with <a
shape="rect" href="http://cxf.apache.org";>Apache CXF</a> for connecting to
JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1423153164721 {padding: 0px;}
-div.rbtoc1423153164721 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1423153164721 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1423203446841 {padding: 0px;}
+div.rbtoc1423203446841 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1423203446841 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1423153164721">
+/*]]>*/</style></p><div class="toc-macro rbtoc1423203446841">
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF
Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI
format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#CXF-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
@@ -29830,22 +29830,14 @@ validator:someLocalOrRemoteResource
</div></div><h3 id="BookInOnePage-URIformat.74">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[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&option=value&...</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 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&option=value&...</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">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[$in.setHeader('fruit',
'Apple')
]]></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>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
intance. </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 </strong>just like
this</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</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 </strong>just like
this</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[ VelocityContext velocityContext = new
VelocityContext(variableMap);
exchange.getIn().setHeader("CamelVelocityContext",
velocityContext);
]]></script>
-</div></div><p> </p><h3 id="BookInOnePage-Hotreloading.2">Hot
reloading</h3><p>The Velocity template resource is, by default, hot reloadable
for both file and classpath resources (expanded jar). If you set
<code>contentCache=true</code>, Camel will only load the resource once, and
thus hot reloading is not possible. This scenario can be used in production,
when the resource never changes.</p><h3
id="BookInOnePage-Dynamictemplates.1">Dynamic
templates</h3><p><strong>Available as of Camel 2.1</strong><br clear="none">
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these headers
is set then Camel uses this over the endpoint configured resource. This allows
you to provide a dynamic template at runtime.</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> Type </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> CamelVelocityResourceUri
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> String
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.1:</strong> A URI for the template resource to use instead of the endpoint
configured. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> CamelVelocityTemplate </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> String </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.1:</strong> The template
to use instead of the endpoint configured. </p></td></tr></tbody></table></div>
-</div><h3 id="BookInOnePage-Samples.23">Samples</h3><p>For example you could
use something like</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+</div></div><p> </p><h3 id="BookInOnePage-Hotreloading.2">Hot
reloading</h3><p>The Velocity template resource is, by default, hot reloadable
for both file and classpath resources (expanded jar). If you set
<code>contentCache=true</code>, Camel will only load the resource once, and
thus hot reloading is not possible. This scenario can be used in production,
when the resource never changes.</p><h3
id="BookInOnePage-Dynamictemplates.1">Dynamic
templates</h3><p><strong>Available as of Camel 2.1</strong><br clear="none">
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these headers
is set then Camel uses this over the endpoint configured resource. This allows
you to provide a dynamic template at runtime.</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>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>CamelVelocityResourceUri</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.1:</strong> A URI for the
template resource to use instead of the endpoint
configured.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>CamelVelocityTemplate</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.1:</strong> The template to use instead
of the endpoint configured.</p></td></tr></tbody></table></div></div><h3
id="BookInOnePage-Samples.23">Samples</h3><p>For example you could use
something like</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("activemq:My.Queue").
to("velocity:com/acme/MyResponse.vm");
]]></script>
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 Fri Feb 6 06:18:23 2015
@@ -97,22 +97,14 @@
</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="theme: Default; brush: java; gutter: false"
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&option=value&...</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 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&option=value&...</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">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[$in.setHeader('fruit',
'Apple')
]]></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</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
intance. </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 </strong>just like
this</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</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 </strong>just like
this</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[ VelocityContext velocityContext = new
VelocityContext(variableMap);
exchange.getIn().setHeader("CamelVelocityContext",
velocityContext);
]]></script>
-</div></div><p> </p><h3 id="Velocity-Hotreloading">Hot
reloading</h3><p>The Velocity template resource is, by default, hot reloadable
for both file and classpath resources (expanded jar). If you set
<code>contentCache=true</code>, Camel will only load the resource once, and
thus hot reloading is not possible. This scenario can be used in production,
when the resource never changes.</p><h3 id="Velocity-Dynamictemplates">Dynamic
templates</h3><p><strong>Available as of Camel 2.1</strong><br clear="none">
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these headers
is set then Camel uses this over the endpoint configured resource. This allows
you to provide a dynamic template at runtime.</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> Type </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> CamelVelocityResourceUri
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> String
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.1:</strong> A URI for the template resource to use instead of the endpoint
configured. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> CamelVelocityTemplate </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> String </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.1:</strong> The template
to use instead of the endpoint configured. </p></td></tr></tbody></table></div>
-</div><h3 id="Velocity-Samples">Samples</h3><p>For example you could use
something like</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><p> </p><h3 id="Velocity-Hotreloading">Hot
reloading</h3><p>The Velocity template resource is, by default, hot reloadable
for both file and classpath resources (expanded jar). If you set
<code>contentCache=true</code>, Camel will only load the resource once, and
thus hot reloading is not possible. This scenario can be used in production,
when the resource never changes.</p><h3 id="Velocity-Dynamictemplates">Dynamic
templates</h3><p><strong>Available as of Camel 2.1</strong><br clear="none">
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these headers
is set then Camel uses this over the endpoint configured resource. This allows
you to provide a dynamic template at runtime.</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="co
nfluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>CamelVelocityResourceUri</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.1:</strong> A URI for the
template resource to use instead of the endpoint
configured.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>CamelVelocityTemplate</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.1:</strong> The template to use instead
of the endpoint configured.</p></td></tr></tbody></table></div></div><h3
id="Velocity-Samples">Samples</h3><p>For example you could use something
like</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("activemq:My.Queue").
to("velocity:com/acme/MyResponse.vm");
]]></script>
