Author: buildbot
Date: Wed Oct 7 11:21:45 2015
New Revision: 968066
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/book-pattern-appendix.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/splitter.html
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Wed Oct 7 11:21:45
2015
@@ -3700,11 +3700,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.rbtoc1443871117117 {padding: 0px;}
-div.rbtoc1443871117117 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1443871117117 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1444216739964 {padding: 0px;}
+div.rbtoc1444216739964 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1444216739964 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1443871117117">
+/*]]>*/</style></p><div class="toc-macro rbtoc1444216739964">
<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>
@@ -3793,7 +3793,7 @@ public class ServerRoutes extends RouteB
//from("jms:queue:numbers").bean("multiplier",
"multiply");
// the same as above but expressed as a URI configuration
-
//from("jms:queue:numbers").to("bean:multiplier?methodName=multiply");
+
//from("jms:queue:numbers").to("bean:multiplier?method=multiply");
}
}
@@ -5809,11 +5809,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.rbtoc1443871117498 {padding: 0px;}
-div.rbtoc1443871117498 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1443871117498 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1444216740671 {padding: 0px;}
+div.rbtoc1444216740671 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1444216740671 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1443871117498">
+/*]]>*/</style><div class="toc-macro rbtoc1444216740671">
<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>
@@ -13058,7 +13058,7 @@ from("direct:streaming")
ExecutorService pool = ...
from("activemq:my.queue")
- .split(xPathBuilder).parallelProcessing().executorService(pool)
+ .split(xPathBuilder).executorService(pool)
.to("activemq:my.parts");
]]></script>
</div></div><h4 id="BookInOnePage-UsingaPojotodothesplitting">Using a Pojo to
do the splitting</h4><p>As the <a shape="rect"
href="splitter.html">Splitter</a> can use any <a shape="rect"
href="expression.html">Expression</a> to do the actual splitting we leverage
this fact and use a <strong>method</strong> expression to invoke a <a
shape="rect" href="bean.html">Bean</a> to get the splitted parts.<br
clear="none"> The <a shape="rect" href="bean.html">Bean</a> should return a
value that is iterable such as: <code>java.util.Collection,
java.util.Iterator</code> or an array. <br clear="none"> So the returned value,
will then be used by Camel at runtime, to split the message.</p><div
class="confluence-information-macro confluence-information-macro-tip"><p
class="title">Streaming mode and using pojo</p><span class="aui-icon
aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When you have enabled the
streaming mod
e, then you should return a <code>Iterator</code> to ensure streamish fashion.
For example if the message is a big file, then by using an iterator, that
returns a piece of the file in chunks, in the <code>next</code> method of the
<code>Iterator</code> ensures low memory footprint. This avoids the need for
reading the entire content into memory. For an example see the source code for
the <a shape="rect" class="external-link"
href="https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apache/camel/support/TokenPairExpressionIterator.java";>TokenizePair</a>
implementation.</p></div></div><p>In the route we define the <a shape="rect"
href="expression.html">Expression</a> as a method call to invoke our <a
shape="rect" href="bean.html">Bean</a> that we have registered with the id
mySplitterBean in the <a shape="rect"
href="registry.html">Registry</a>.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -17426,11 +17426,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.rbtoc1443871120036 {padding: 0px;}
-div.rbtoc1443871120036 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1443871120036 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1444216766004 {padding: 0px;}
+div.rbtoc1444216766004 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1444216766004 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1443871120036">
+/*]]>*/</style></p><div class="toc-macro rbtoc1444216766004">
<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/book-pattern-appendix.html
==============================================================================
--- websites/production/camel/content/book-pattern-appendix.html (original)
+++ websites/production/camel/content/book-pattern-appendix.html Wed Oct 7
11:21:45 2015
@@ -1424,7 +1424,7 @@ from("direct:streaming")
ExecutorService pool = ...
from("activemq:my.queue")
- .split(xPathBuilder).parallelProcessing().executorService(pool)
+ .split(xPathBuilder).executorService(pool)
.to("activemq:my.parts");
]]></script>
</div></div><h4 id="BookPatternAppendix-UsingaPojotodothesplitting">Using a
Pojo to do the splitting</h4><p>As the <a shape="rect"
href="splitter.html">Splitter</a> can use any <a shape="rect"
href="expression.html">Expression</a> to do the actual splitting we leverage
this fact and use a <strong>method</strong> expression to invoke a <a
shape="rect" href="bean.html">Bean</a> to get the splitted parts.<br
clear="none"> The <a shape="rect" href="bean.html">Bean</a> should return a
value that is iterable such as: <code>java.util.Collection,
java.util.Iterator</code> or an array. <br clear="none"> So the returned value,
will then be used by Camel at runtime, to split the message.</p><div
class="confluence-information-macro confluence-information-macro-tip"><p
class="title">Streaming mode and using pojo</p><span class="aui-icon
aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When you have enabled the streami
ng mode, then you should return a <code>Iterator</code> to ensure streamish
fashion. For example if the message is a big file, then by using an iterator,
that returns a piece of the file in chunks, in the <code>next</code> method of
the <code>Iterator</code> ensures low memory footprint. This avoids the need
for reading the entire content into memory. For an example see the source code
for the <a shape="rect" class="external-link"
href="https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apache/camel/support/TokenPairExpressionIterator.java";>TokenizePair</a>
implementation.</p></div></div><p>In the route we define the <a shape="rect"
href="expression.html">Expression</a> as a method call to invoke our <a
shape="rect" href="bean.html">Bean</a> that we have registered with the id
mySplitterBean in the <a shape="rect"
href="registry.html">Registry</a>.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/splitter.html
==============================================================================
--- websites/production/camel/content/splitter.html (original)
+++ websites/production/camel/content/splitter.html Wed Oct 7 11:21:45 2015
@@ -248,7 +248,7 @@ from("direct:streaming")
ExecutorService pool = ...
from("activemq:my.queue")
- .split(xPathBuilder).parallelProcessing().executorService(pool)
+ .split(xPathBuilder).executorService(pool)
.to("activemq:my.parts");
]]></script>
</div></div><h4 id="Splitter-UsingaPojotodothesplitting">Using a Pojo to do
the splitting</h4><p>As the <a shape="rect" href="splitter.html">Splitter</a>
can use any <a shape="rect" href="expression.html">Expression</a> to do the
actual splitting we leverage this fact and use a <strong>method</strong>
expression to invoke a <a shape="rect" href="bean.html">Bean</a> to get the
splitted parts.<br clear="none"> The <a shape="rect" href="bean.html">Bean</a>
should return a value that is iterable such as: <code>java.util.Collection,
java.util.Iterator</code> or an array. <br clear="none"> So the returned value,
will then be used by Camel at runtime, to split the message.</p><div
class="confluence-information-macro confluence-information-macro-tip"><p
class="title">Streaming mode and using pojo</p><span class="aui-icon
aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When you have enabled the
streaming mode, th
en you should return a <code>Iterator</code> to ensure streamish fashion. For
example if the message is a big file, then by using an iterator, that returns a
piece of the file in chunks, in the <code>next</code> method of the
<code>Iterator</code> ensures low memory footprint. This avoids the need for
reading the entire content into memory. For an example see the source code for
the <a shape="rect" class="external-link"
href="https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apache/camel/support/TokenPairExpressionIterator.java";>TokenizePair</a>
implementation.</p></div></div><p>In the route we define the <a shape="rect"
href="expression.html">Expression</a> as a method call to invoke our <a
shape="rect" href="bean.html">Bean</a> that we have registered with the id
mySplitterBean in the <a shape="rect"
href="registry.html">Registry</a>.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
