Author: buildbot
Date: Tue Jun 23 10:19:38 2015
New Revision: 955753
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/dead-letter-channel.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 Tue Jun 23 10:19:38
2015
@@ -3876,11 +3876,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.rbtoc1435047520743 {padding: 0px;}
-div.rbtoc1435047520743 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1435047520743 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1435054712004 {padding: 0px;}
+div.rbtoc1435054712004 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1435054712004 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1435047520743">
+/*]]>*/</style></p><div class="toc-macro rbtoc1435054712004">
<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>
@@ -6066,11 +6066,11 @@ So we completed the last piece in the pi
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1435047521187 {padding: 0px;}
-div.rbtoc1435047521187 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1435047521187 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1435054712416 {padding: 0px;}
+div.rbtoc1435054712416 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1435054712416 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1435047521187">
+/*]]>*/</style><div class="toc-macro rbtoc1435054712416">
<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>
@@ -12886,7 +12886,7 @@ RouteBuilder builder = new RouteBuilder(
</div></div><p>The route listen for JMS messages and validates, transforms and
handle it. During this the <a shape="rect" href="exchange.html">Exchange</a>
payload is transformed/modified. So in case something goes wrong and we want to
move the message to another JMS destination, then we can configure our <a
shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> with the
<strong>useOriginalMessage</strong> option. But when we move the <a
shape="rect" href="exchange.html">Exchange</a> to this destination we do not
know in which state the message is in. Did the error happen in before the
transformOrder or after? So to be sure we want to move the original input
message we received from <code>jms:queue:order:input</code>. So we can do this
by enabling the <strong>useOriginalMessage</strong> option as shown
below:</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[ // will use original body
errorHandler(deadLetterChannel("jms:queue:dead")
- .useOriginalMessage().mamimumRedeliveries(5).redeliverDelay(5000);
+ .useOriginalMessage().maximumRedeliveries(5).redeliverDelay(5000);
]]></script>
</div></div><p>Then the messages routed to the <code>jms:queue:dead</code> is
the original input. If we want to manually retry we can move the JMS message
from the failed to the input queue, with no problem as the message is the same
as the original we received.</p><h3
id="BookInOnePage-OnRedelivery">OnRedelivery</h3><p>When <a shape="rect"
href="dead-letter-channel.html">Dead Letter Channel</a> is doing redeliver its
possible to configure a <a shape="rect" href="processor.html">Processor</a>
that is executed just <strong>before</strong> every redelivery attempt. This
can be used for the situations where you need to alter the message before its
redelivered. See below for sample.</p> <div class="aui-message success
shadowed information-macro">
<p class="title">onException and onRedeliver</p>
@@ -18653,11 +18653,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.rbtoc1435047541373 {padding: 0px;}
-div.rbtoc1435047541373 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1435047541373 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1435054724692 {padding: 0px;}
+div.rbtoc1435054724692 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1435054724692 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1435047541373">
+/*]]>*/</style></p><div class="toc-macro rbtoc1435054724692">
<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>
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 Tue Jun 23
10:19:38 2015
@@ -484,7 +484,7 @@ RouteBuilder builder = new RouteBuilder(
</div></div><p>The route listen for JMS messages and validates, transforms and
handle it. During this the <a shape="rect" href="exchange.html">Exchange</a>
payload is transformed/modified. So in case something goes wrong and we want to
move the message to another JMS destination, then we can configure our <a
shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> with the
<strong>useOriginalMessage</strong> option. But when we move the <a
shape="rect" href="exchange.html">Exchange</a> to this destination we do not
know in which state the message is in. Did the error happen in before the
transformOrder or after? So to be sure we want to move the original input
message we received from <code>jms:queue:order:input</code>. So we can do this
by enabling the <strong>useOriginalMessage</strong> option as shown
below:</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[ // will use original body
errorHandler(deadLetterChannel("jms:queue:dead")
- .useOriginalMessage().mamimumRedeliveries(5).redeliverDelay(5000);
+ .useOriginalMessage().maximumRedeliveries(5).redeliverDelay(5000);
]]></script>
</div></div><p>Then the messages routed to the <code>jms:queue:dead</code> is
the original input. If we want to manually retry we can move the JMS message
from the failed to the input queue, with no problem as the message is the same
as the original we received.</p><h3
id="BookPatternAppendix-OnRedelivery">OnRedelivery</h3><p>When <a shape="rect"
href="dead-letter-channel.html">Dead Letter Channel</a> is doing redeliver its
possible to configure a <a shape="rect" href="processor.html">Processor</a>
that is executed just <strong>before</strong> every redelivery attempt. This
can be used for the situations where you need to alter the message before its
redelivered. See below for sample.</p> <div class="aui-message success
shadowed information-macro">
<p class="title">onException and onRedeliver</p>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/dead-letter-channel.html
==============================================================================
--- websites/production/camel/content/dead-letter-channel.html (original)
+++ websites/production/camel/content/dead-letter-channel.html Tue Jun 23
10:19:38 2015
@@ -122,7 +122,7 @@
</div></div><p>The route listen for JMS messages and validates, transforms and
handle it. During this the <a shape="rect" href="exchange.html">Exchange</a>
payload is transformed/modified. So in case something goes wrong and we want to
move the message to another JMS destination, then we can configure our <a
shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> with the
<strong>useOriginalMessage</strong> option. But when we move the <a
shape="rect" href="exchange.html">Exchange</a> to this destination we do not
know in which state the message is in. Did the error happen in before the
transformOrder or after? So to be sure we want to move the original input
message we received from <code>jms:queue:order:input</code>. So we can do this
by enabling the <strong>useOriginalMessage</strong> option as shown
below:</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[ // will use original body
errorHandler(deadLetterChannel("jms:queue:dead")
- .useOriginalMessage().mamimumRedeliveries(5).redeliverDelay(5000);
+ .useOriginalMessage().maximumRedeliveries(5).redeliverDelay(5000);
]]></script>
</div></div><p>Then the messages routed to the <code>jms:queue:dead</code> is
the original input. If we want to manually retry we can move the JMS message
from the failed to the input queue, with no problem as the message is the same
as the original we received.</p><h3
id="DeadLetterChannel-OnRedelivery">OnRedelivery</h3><p>When <a shape="rect"
href="dead-letter-channel.html">Dead Letter Channel</a> is doing redeliver its
possible to configure a <a shape="rect" href="processor.html">Processor</a>
that is executed just <strong>before</strong> every redelivery attempt. This
can be used for the situations where you need to alter the message before its
redelivered. See below for sample.</p> <div class="aui-message success
shadowed information-macro">
<p class="title">onException and onRedeliver</p>
