Author: buildbot
Date: Sun Mar 20 15:20:07 2016
New Revision: 983254
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/cassandra.html
websites/production/camel/content/class.html
websites/production/camel/content/http4.html
Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Sun Mar 20
15:20:07 2016
@@ -668,7 +668,7 @@ browse:someName[?options]
</div></div><p>You can get cache hits, misses, in-memory hits, disk hits, size
stats this way. You can also change CacheConfiguration parameters on the
fly.</p><h3 id="BookComponentAppendix-CachereplicationCamel2.8+">Cache
replication Camel 2.8+</h3><p>The Camel Cache component is able to distribute a
cache across server nodes using several different replication mechanisms
including: RMI, JGroups, JMS and Cache Server.</p><p>There are two different
ways to make it work:</p><p><strong>1.</strong> You can configure
<code>ehcache.xml</code> manually</p><p>OR</p><p><strong>2.</strong> You can
configure these three options:</p><ul
class="alternate"><li>cacheManagerFactory</li><li>eventListenerRegistry</li><li>cacheLoaderRegistry</li></ul><p>Configuring
Camel Cache replication using the first option is a bit of hard work as you
have to configure all caches separately. So in a situation when the all names
of caches are not known, using <code>ehcache.xml</code> is not a good
idea.</p><p>The
second option is much better when you want to use many different caches as
you do not need to define options per cache. This is because replication
options are set per <code>CacheManager</code> and per
<code>CacheEndpoint</code>. Also it is the only way when cache names are not
know at the development phase.</p><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>It might be useful to read the <a
shape="rect" class="external-link" href="http://ehcache.org/documentation";
rel="nofollow">EHCache manual</a> to get a better understanding of the Camel
Cache replication mechanism.</p></div></div><h4
id="BookComponentAppendix-Example:JMScachereplication">Example: JMS cache
replication</h4><p>JMS replication is the most powerful and secured replication
method. Used together with Camel Cache replication makes it also rath
er simple.<br clear="none"> An example is available on <a shape="rect"
href="cachereplicationjmsexample.html">a separate page</a>.</p> <h2
id="BookComponentAppendix-ClassComponent">Class
Component</h2><p><strong>Available as of Camel 2.4</strong></p><p>The
<strong>class:</strong> component binds beans to Camel message exchanges. It
works in the same way as the <a shape="rect" href="bean.html">Bean</a>
component but instead of looking up beans from a <a shape="rect"
href="registry.html">Registry</a> it creates the bean based on the class
name.</p><h3 id="BookComponentAppendix-URIformat.6">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[class:className[?options]
]]></script>
-</div></div><p>Where <strong>className</strong> is the fully qualified class
name to create and use as bean.</p><h3
id="BookComponentAppendix-Options.4">Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>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>method</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The method name that bean will be invoked.
If not provided, Camel will try to pick the method itself. In case of ambiguity
an exception is thrown. See <a shape="re
ct" href="bean-binding.html">Bean Binding</a> for more
details.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>multiParameterArray</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>How to treat the parameters which are
passed from the message body; if it is <code>true</code>, the In message body
should be an array of parameters.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>bean.xxx</code></td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><code>null</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><strong>Camel 2.17:</strong> To configure additional
options on the create bean instance from the class name. For example to
configure a foo option on the bean, use bean.foo=123.</td></tr><
/tbody></table></div></div><p>You can append query options to the URI in the
following format, <code>?option=value&option=value&...</code></p><h3
id="BookComponentAppendix-Using.1">Using</h3><p>You simply use the
<strong>class</strong> component just as the <a shape="rect"
href="bean.html">Bean</a> component but by specifying the fully qualified
classname instead.<br clear="none"> For example to use the
<code>MyFooBean</code> you have to do as follows:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Where <strong>className</strong> is the fully qualified class
name to create and use as bean.</p><h3
id="BookComponentAppendix-Options.4">Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>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>method</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The method name that bean will be invoked.
If not provided, Camel will try to pick the method itself. In case of ambiguity
an exception is thrown. See <a shape="re
ct" href="bean-binding.html">Bean Binding</a> for more
details.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>multiParameterArray</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>How to treat the parameters which are
passed from the message body; if it is <code>true</code>, the In message body
should be an array of parameters.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>bean.xxx</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.17:</strong> To configure additional
options on the create bean instance from the class name. For example to
configure a foo option on the bean, use bean.fo
o=123.</p></td></tr></tbody></table></div></div><p>You can append query
options to the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="BookComponentAppendix-Using.1">Using</h3><p>You simply use the
<strong>class</strong> component just as the <a shape="rect"
href="bean.html">Bean</a> component but by specifying the fully qualified
classname instead.<br clear="none"> For example to use the
<code>MyFooBean</code> you have to do as follows:</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[
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean").to("mock:result");
]]></script>
</div></div><p>You can also specify which method to invoke on the
<code>MyFooBean</code>, for example <code>hello</code>:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -1016,11 +1016,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.rbtoc1458483461721 {padding: 0px;}
-div.rbtoc1458483461721 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1458483461721 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1458487101472 {padding: 0px;}
+div.rbtoc1458487101472 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1458487101472 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1458483461721">
+/*]]>*/</style></p><div class="toc-macro rbtoc1458487101472">
<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>
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Sun Mar 20 15:20:07
2016
@@ -3724,11 +3724,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> </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.rbtoc1458483513127 {padding: 0px;}
-div.rbtoc1458483513127 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1458483513127 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1458487121230 {padding: 0px;}
+div.rbtoc1458487121230 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1458487121230 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1458483513127">
+/*]]>*/</style></p><div class="toc-macro rbtoc1458487121230">
<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>
@@ -5843,11 +5843,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.rbtoc1458483513713 {padding: 0px;}
-div.rbtoc1458483513713 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1458483513713 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1458487121785 {padding: 0px;}
+div.rbtoc1458487121785 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1458487121785 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1458483513713">
+/*]]>*/</style><div class="toc-macro rbtoc1458487121785">
<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>
@@ -16928,7 +16928,7 @@ browse:someName[?options]
</div></div><p>You can get cache hits, misses, in-memory hits, disk hits, size
stats this way. You can also change CacheConfiguration parameters on the
fly.</p><h3 id="BookInOnePage-CachereplicationCamel2.8+">Cache replication
Camel 2.8+</h3><p>The Camel Cache component is able to distribute a cache
across server nodes using several different replication mechanisms including:
RMI, JGroups, JMS and Cache Server.</p><p>There are two different ways to make
it work:</p><p><strong>1.</strong> You can configure <code>ehcache.xml</code>
manually</p><p>OR</p><p><strong>2.</strong> You can configure these three
options:</p><ul
class="alternate"><li>cacheManagerFactory</li><li>eventListenerRegistry</li><li>cacheLoaderRegistry</li></ul><p>Configuring
Camel Cache replication using the first option is a bit of hard work as you
have to configure all caches separately. So in a situation when the all names
of caches are not known, using <code>ehcache.xml</code> is not a good
idea.</p><p>The second
option is much better when you want to use many different caches as you do not
need to define options per cache. This is because replication options are set
per <code>CacheManager</code> and per <code>CacheEndpoint</code>. Also it is
the only way when cache names are not know at the development phase.</p><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>It might be useful to read the <a
shape="rect" class="external-link" href="http://ehcache.org/documentation";
rel="nofollow">EHCache manual</a> to get a better understanding of the Camel
Cache replication mechanism.</p></div></div><h4
id="BookInOnePage-Example:JMScachereplication">Example: JMS cache
replication</h4><p>JMS replication is the most powerful and secured replication
method. Used together with Camel Cache replication makes it also rather
simple.<br cl
ear="none"> An example is available on <a shape="rect"
href="cachereplicationjmsexample.html">a separate page</a>.</p> <h2
id="BookInOnePage-ClassComponent">Class Component</h2><p><strong>Available as
of Camel 2.4</strong></p><p>The <strong>class:</strong> component binds beans
to Camel message exchanges. It works in the same way as the <a shape="rect"
href="bean.html">Bean</a> component but instead of looking up beans from a <a
shape="rect" href="registry.html">Registry</a> it creates the bean based on the
class name.</p><h3 id="BookInOnePage-URIformat.7">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[class:className[?options]
]]></script>
-</div></div><p>Where <strong>className</strong> is the fully qualified class
name to create and use as bean.</p><h3
id="BookInOnePage-Options.25">Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>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>method</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The method name that bean will be invoked.
If not provided, Camel will try to pick the method itself. In case of ambiguity
an exception is thrown. See <a shape="rect" hre
f="bean-binding.html">Bean Binding</a> for more details.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>multiParameterArray</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>How to treat the parameters which are
passed from the message body; if it is <code>true</code>, the In message body
should be an array of parameters.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>bean.xxx</code></td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><code>null</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><strong>Camel 2.17:</strong> To configure additional
options on the create bean instance from the class name. For example to
configure a foo option on the bean, use bean.foo=123.</td></tr></tbody>
</table></div></div><p>You can append query options to the URI in the
following format, <code>?option=value&option=value&...</code></p><h3
id="BookInOnePage-Using.1">Using</h3><p>You simply use the
<strong>class</strong> component just as the <a shape="rect"
href="bean.html">Bean</a> component but by specifying the fully qualified
classname instead.<br clear="none"> For example to use the
<code>MyFooBean</code> you have to do as follows:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Where <strong>className</strong> is the fully qualified class
name to create and use as bean.</p><h3
id="BookInOnePage-Options.25">Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>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>method</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The method name that bean will be invoked.
If not provided, Camel will try to pick the method itself. In case of ambiguity
an exception is thrown. See <a shape="rect" hre
f="bean-binding.html">Bean Binding</a> for more details.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>multiParameterArray</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>How to treat the parameters which are
passed from the message body; if it is <code>true</code>, the In message body
should be an array of parameters.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>bean.xxx</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.17:</strong> To configure additional
options on the create bean instance from the class name. For example to
configure a foo option on the bean, use bean.foo=123.<
/p></td></tr></tbody></table></div></div><p>You can append query options to
the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="BookInOnePage-Using.1">Using</h3><p>You simply use the
<strong>class</strong> component just as the <a shape="rect"
href="bean.html">Bean</a> component but by specifying the fully qualified
classname instead.<br clear="none"> For example to use the
<code>MyFooBean</code> you have to do as follows:</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[
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean").to("mock:result");
]]></script>
</div></div><p>You can also specify which method to invoke on the
<code>MyFooBean</code>, for example <code>hello</code>:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -17276,11 +17276,11 @@ template.send("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.rbtoc1458483570656 {padding: 0px;}
-div.rbtoc1458483570656 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1458483570656 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1458487126670 {padding: 0px;}
+div.rbtoc1458487126670 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1458487126670 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1458483570656">
+/*]]>*/</style></p><div class="toc-macro rbtoc1458487126670">
<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>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/cassandra.html
==============================================================================
--- websites/production/camel/content/cassandra.html (original)
+++ websites/production/camel/content/cassandra.html Sun Mar 20 15:20:07 2016
@@ -92,7 +92,7 @@
<version>x.y.z</version>
<!-- use the same version as your Camel core version -->
</dependency>]]></script>
-</div></div><h2 id="Cassandra-URIformat">URI format</h2><p>The endpoint can
initiate the Cassandra connection or use an existing one.</p><div
class="table-wrap"><table class="confluenceTable"><thead><tr><th colspan="1"
rowspan="1" class="confluenceTh">URI</th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th></tr></thead><tbody><tr><td colspan="1"
rowspan="1" class="confluenceTd"><code>cql:localhost/keyspace</code></td><td
colspan="1" rowspan="1" class="confluenceTd">Single host, default port, usual
for testing</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>cql:host1,host2/keyspace</code></td><td colspan="1"
rowspan="1" class="confluenceTd">Multi host, default port</td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><code>cql:host1,host2:9042/keyspace</code></td><td
colspan="1" rowspan="1" class="confluenceTd">Multi host, custom
port</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>cql:host1,host2</code></td><td colspa
n="1" rowspan="1" class="confluenceTd">Default port and
keyspace</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>cql:bean:sessionRef</code></td><td colspan="1"
rowspan="1" class="confluenceTd">Provided Session reference</td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><code>cql:bean:clusterRef/keyspace</code></td><td
colspan="1" rowspan="1" class="confluenceTd">Provided Cluster
reference</td></tr></tbody></table></div><p>To fine tune the Cassandra
connection (SSL options, pooling options, load balancing policy, retry policy,
reconnection policy...), create your own Cluster instance and give it to the
Camel endpoint.</p><h2 id="Cassandra-EndpointOptions">Endpoint Options</h2><div
class="table-wrap"><table class="confluenceTable"><thead><tr><th colspan="1"
rowspan="1" class="confluenceTh">Option</th><th colspan="1" rowspan="1"
class="confluenceTh">Default</th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th></tr></thead><tbody><tr><td c
olspan="1" rowspan="1"
class="confluenceTd"><p><code>clusterName</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Cluster name</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>username and
password</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Session authentication</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>cql</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p>CQL query. Can be overriden with a message
header.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>consistencyLevel</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>ANY</code>, <code>ONE</code>, <code>TWO</code>,
<code>QUORUM</c
ode>, <code>LOCAL_QUORUM</code>...</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><code>prepareStatements</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>true</code></td><td
colspan="1" rowspan="1" class="confluenceTd">Use prepared statement (default)
or not</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>resultSetConversionStrategy</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>ALL</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>How is ResultSet converted
transformed into message body <code>ALL</code>, <code>ONE</code>,
<code>LIMIT_10</code>,
<code>LIMIT_100</code>...</p></td></tr></tbody></table></div><h2
id="Cassandra-Messages">Messages</h2><h3
id="Cassandra-IncomingMessage">Incoming Message</h3><p>The Camel Cassandra
endpoint expects a bunch of simple objects (<code>Object</code> or
<code>Object[]</code> or <code>Collection<Object></code>) which will be
bound to the CQL statem
ent as query parameters. If message body is null or empty, then  CQL
query will be executed without binding parameters.</p><p>Headers:</p><ul
class="task-list"><li><code>CamelCqlQuery</code> (optional, <code>String</code>
or <code>RegularStatement</code>): CQL query either as a plain String or built
using the <code>QueryBuilder</code>.</li></ul><h3
id="Cassandra-OutgoingMessage">Outgoing Message</h3><p>The Camel Cassandra
endpoint produces one or many a Cassandra Row objects depending on
the <code>resultSetConversionStrategy</code>:</p><p> </p><ul><li><code>List<Row></code>
if <code>resultSetConversionStrategy</code> is <code>ALL</code> or
<code>LIMIT_[0-9]+</code></li><li>Single<code> Row</code> if
<code>resultSetConversionStrategy</code> is <code>ONE</code></li><li>Anything
else, if <code>resultSetConversionStrategy</code> is a custom implementation of
the <code>ResultSetConversionStrategy</code></li></ul><h2
id="Cassandra-Repositories">Repositories</h2><p>Cas
sandra can be used to store message keys or messages for the idempotent and
aggregation EIP.</p><p>Cassandra might not be the best tool for queuing use
cases yet, read <a shape="rect" class="external-link"
href="http://www.datastax.com/dev/blog/cassandra-anti-patterns-queues-and-queue-like-datasets";
rel="nofollow">Cassandra anti-patterns queues and queue like datasets</a>.
It's advised to use LeveledCompaction and a small GC grace setting for these
tables to allow tombstoned rows to be removed quickly.</p><h3
id="Cassandra-Idempotentrepository">Idempotent repository</h3><p>The
<code>NamedCassandraIdempotentRepository</code> stores messages keys in a
Cassandra table like this:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width:
1px;"><b>CAMEL_IDEMPOTENT.cql</b></div><div class="codeContent panelContent
pdl">
+</div></div><h2 id="Cassandra-URIformat">URI format</h2><p>The endpoint can
initiate the Cassandra connection or use an existing one.</p><div
class="table-wrap"><table class="confluenceTable"><thead><tr><th colspan="1"
rowspan="1" class="confluenceTh">URI</th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th></tr></thead><tbody><tr><td colspan="1"
rowspan="1" class="confluenceTd"><code>cql:localhost/keyspace</code></td><td
colspan="1" rowspan="1" class="confluenceTd">Single host, default port, usual
for testing</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>cql:host1,host2/keyspace</code></td><td colspan="1"
rowspan="1" class="confluenceTd">Multi host, default port</td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><code>cql:host1,host2:9042/keyspace</code></td><td
colspan="1" rowspan="1" class="confluenceTd">Multi host, custom
port</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>cql:host1,host2</code></td><td colspa
n="1" rowspan="1" class="confluenceTd">Default port and
keyspace</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>cql:bean:sessionRef</code></td><td colspan="1"
rowspan="1" class="confluenceTd">Provided Session reference</td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><code>cql:bean:clusterRef/keyspace</code></td><td
colspan="1" rowspan="1" class="confluenceTd">Provided Cluster
reference</td></tr></tbody></table></div><p>To fine tune the Cassandra
connection (SSL options, pooling options, load balancing policy, retry policy,
reconnection policy...), create your own Cluster instance and give it to the
Camel endpoint.</p><h2 id="Cassandra-EndpointOptions">Endpoint Options</h2><div
class="table-wrap"><table class="confluenceTable"><thead><tr><th colspan="1"
rowspan="1" class="confluenceTh">Option</th><th colspan="1" rowspan="1"
class="confluenceTh">Default</th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th></tr></thead><tbody><tr><td c
olspan="1" rowspan="1"
class="confluenceTd"><p><code>clusterName</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Cluster name</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>username and
password</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Session authentication</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>cql</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p>CQL query. Can be overriden with a message
header.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>consistencyLevel</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>ANY</code>, <code>ONE</code>, <code>TWO</code>,
<code>QUORUM</c
ode>, <code>LOCAL_QUORUM</code>...</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>prepareStatements</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Use prepared statement
(default) or not</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>resultSetConversionStrategy</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>ALL</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>How is ResultSet converted
transformed into message body <code>ALL</code>, <code>ONE</code>,
<code>LIMIT_10</code>,
<code>LIMIT_100</code>...</p></td></tr></tbody></table></div><h2
id="Cassandra-Messages">Messages</h2><h3
id="Cassandra-IncomingMessage">Incoming Message</h3><p>The Camel Cassandra
endpoint expects a bunch of simple objects (<code>Object</code> or
<code>Object[]</code> or <code>Collection<Object></code>) which will be bo
und to the CQL statement as query parameters. If message body is null or
empty, then  CQL query will be executed without binding
parameters.</p><p>Headers:</p><ul
class="task-list"><li><code>CamelCqlQuery</code> (optional, <code>String</code>
or <code>RegularStatement</code>): CQL query either as a plain String or built
using the <code>QueryBuilder</code>.</li></ul><h3
id="Cassandra-OutgoingMessage">Outgoing Message</h3><p>The Camel Cassandra
endpoint produces one or many a Cassandra Row objects depending on
the <code>resultSetConversionStrategy</code>:</p><p> </p><ul><li><code>List<Row></code>
if <code>resultSetConversionStrategy</code> is <code>ALL</code> or
<code>LIMIT_[0-9]+</code></li><li>Single<code> Row</code> if
<code>resultSetConversionStrategy</code> is <code>ONE</code></li><li>Anything
else, if <code>resultSetConversionStrategy</code> is a custom implementation of
the <code>ResultSetConversionStrategy</code></li></ul><h2
id="Cassandra-Repositories">Re
positories</h2><p>Cassandra can be used to store message keys or messages for
the idempotent and aggregation EIP.</p><p>Cassandra might not be the best tool
for queuing use cases yet, read <a shape="rect" class="external-link"
href="http://www.datastax.com/dev/blog/cassandra-anti-patterns-queues-and-queue-like-datasets";
rel="nofollow">Cassandra anti-patterns queues and queue like datasets</a>.
It's advised to use LeveledCompaction and a small GC grace setting for these
tables to allow tombstoned rows to be removed quickly.</p><h3
id="Cassandra-Idempotentrepository">Idempotent repository</h3><p>The
<code>NamedCassandraIdempotentRepository</code> stores messages keys in a
Cassandra table like this:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width:
1px;"><b>CAMEL_IDEMPOTENT.cql</b></div><div class="codeContent panelContent
pdl">
<script class="brush: sql; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[CREATE TABLE CAMEL_IDEMPOTENT (
NAME varchar, -- Repository name
KEY varchar, -- Message key
Modified: websites/production/camel/content/class.html
==============================================================================
--- websites/production/camel/content/class.html (original)
+++ websites/production/camel/content/class.html Sun Mar 20 15:20:07 2016
@@ -87,7 +87,7 @@
<div class="wiki-content maincontent"><h2 id="Class-ClassComponent">Class
Component</h2><p><strong>Available as of Camel 2.4</strong></p><p>The
<strong>class:</strong> component binds beans to Camel message exchanges. It
works in the same way as the <a shape="rect" href="bean.html">Bean</a>
component but instead of looking up beans from a <a shape="rect"
href="registry.html">Registry</a> it creates the bean based on the class
name.</p><h3 id="Class-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[class:className[?options]
]]></script>
-</div></div><p>Where <strong>className</strong> is the fully qualified class
name to create and use as bean.</p><h3 id="Class-Options">Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>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>method</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The method name that bean will be invoked.
If not provided, Camel will try to pick the method itself. In case of ambiguity
an exception is thrown. See <a shape="rect" href="bean-bin
ding.html">Bean Binding</a> for more details.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>multiParameterArray</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>How to treat the parameters which are
passed from the message body; if it is <code>true</code>, the In message body
should be an array of parameters.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>bean.xxx</code></td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><code>null</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><strong>Camel 2.17:</strong> To configure additional
options on the create bean instance from the class name. For example to
configure a foo option on the bean, use
bean.foo=123.</td></tr></tbody></table></d
iv></div><p>You can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="Class-Using">Using</h3><p>You simply use the <strong>class</strong>
component just as the <a shape="rect" href="bean.html">Bean</a> component but
by specifying the fully qualified classname instead.<br clear="none"> For
example to use the <code>MyFooBean</code> you have to do as follows:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>Where <strong>className</strong> is the fully qualified class
name to create and use as bean.</p><h3 id="Class-Options">Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>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>method</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The method name that bean will be invoked.
If not provided, Camel will try to pick the method itself. In case of ambiguity
an exception is thrown. See <a shape="rect" href="bean-bin
ding.html">Bean Binding</a> for more details.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>multiParameterArray</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>How to treat the parameters which are
passed from the message body; if it is <code>true</code>, the In message body
should be an array of parameters.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>bean.xxx</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.17:</strong> To configure additional
options on the create bean instance from the class name. For example to
configure a foo option on the bean, use bean.foo=123.</p></td></t
r></tbody></table></div></div><p>You can append query options to the URI in
the following format,
<code>?option=value&option=value&...</code></p><h3
id="Class-Using">Using</h3><p>You simply use the <strong>class</strong>
component just as the <a shape="rect" href="bean.html">Bean</a> component but
by specifying the fully qualified classname instead.<br clear="none"> For
example to use the <code>MyFooBean</code> you have to do as follows:</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[
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean").to("mock:result");
]]></script>
</div></div><p>You can also specify which method to invoke on the
<code>MyFooBean</code>, for example <code>hello</code>:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
