Author: buildbot
Date: Tue Jan 20 15:22:30 2015
New Revision: 936965
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/smpp.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 Tue Jan 20
15:22:30 2015
@@ -1360,11 +1360,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.rbtoc1421687904276 {padding: 0px;}
-div.rbtoc1421687904276 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1421687904276 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1421767099673 {padding: 0px;}
+div.rbtoc1421767099673 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1421767099673 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1421687904276">
+/*]]>*/</style></p><div class="toc-macro rbtoc1421767099673">
<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>
@@ -11305,7 +11305,7 @@ protected RouteBuilder createRouteBuilde
<p><strong>The Camel SIP component also ships with a Presence Agent that is
meant to be used for Testing and Demo purposes only.</strong> An example of
instantiating a Presence Agent is given above. </p>
<p>Note that the Presence Agent is set up as a user agent@localhost:5152 and
is capable of communicating with both Publisher as well as Subscriber. It has a
separate SIP stackName distinct from Publisher as well as Subscriber. While it
is set up as a Camel Consumer, it does not actually send any messages along the
route to the endpoint "mock:neverland".</p>
-<h2 id="BookComponentAppendix-SMPPComponent">SMPP
Component</h2><p><strong>Available as of Camel 2.2</strong></p><p>This
component provides access to an SMSC (Short Message Service Center) over the <a
shape="rect" class="external-link"
href="http://smsforum.net/SMPP_v3_4_Issue1_2.zip"; rel="nofollow">SMPP</a>
protocol to send and receive SMS. The <a shape="rect" class="external-link"
href="http://code.google.com/p/jsmpp/"; rel="nofollow">JSMPP</a> library is used
for the protocol implementation.</p><p>The Camel component currently operates
as an <a shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/ESME"; rel="nofollow">ESME</a> (External
Short Messaging Entity) and not as an SMSC itself.</p><p>Starting with<strong>
Camel 2.9</strong> you are also able to execute ReplaceSm, QuerySm,
SubmitMulti, CancelSm and DataSm.</p><p>Maven users will need to add the
following dependency to their <code>pom.xml</code> for this component:</p><div
class="code panel pdl" style="
border-width: 1px;"><div class="codeContent panelContent pdl">
+<h2 id="BookComponentAppendix-SMPPComponent">SMPP
Component</h2><p><strong>Available as of Camel 2.2</strong></p><p>This
component provides access to an SMSC (Short Message Service Center) over the <a
shape="rect" class="external-link"
href="http://smsforum.net/SMPP_v3_4_Issue1_2.zip"; rel="nofollow">SMPP</a>
protocol to send and receive SMS. The <a shape="rect" class="external-link"
href="http://jsmpp.org"; rel="nofollow">JSMPP</a> library is used for the
protocol implementation.</p><p>The Camel component currently operates as an <a
shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/ESME";
rel="nofollow">ESME</a> (External Short Messaging Entity) and not as an SMSC
itself.</p><p>Starting with<strong> Camel 2.9</strong> you are also able
to execute ReplaceSm, QuerySm, SubmitMulti, CancelSm and DataSm.</p><p>Maven
users will need to add the following dependency to their <code>pom.xml</code>
for this component:</p><div class="code panel pdl" style="border-width: 1
px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-smpp</artifactId>
@@ -11324,10 +11324,10 @@ smpps://[username@]hostname[:port][?opti
<p class="title">JSMPP library</p>
<span class="aui-icon icon-success">Icon</span>
<div class="message-content">
- <p>See the documentation of the <a shape="rect"
class="external-link" href="http://code.google.com/p/jsmpp/";
rel="nofollow">JSMPP Library</a> for more details about the underlying
library.</p>
+ <p>See the documentation of the <a shape="rect"
class="external-link" href="http://jsmpp.org"; rel="nofollow">JSMPP Library</a>
for more details about the underlying library.</p>
</div>
</div>
-<h3 id="BookComponentAppendix-Exceptionhandling.1">Exception
handling</h3><p>This component supports the general Camel exception handling
capabilities</p><p>When an error occurs sending a message with SubmitSm (the
default action), the org.apache.camel.component.smpp.SmppException is thrown
with a nested exception, org.jsmpp.extra.NegativeResponseException.  Call
NegativeResponseException.getCommandStatus() to obtain the exact SMPP negative
response code, the values are explained in the SMPP specification 3.4, section
5.1.3.<br clear="none"> <strong>Camel 2.8 onwards</strong>: When the SMPP
consumer receives a <code>DeliverSm</code> or <code>DataSm</code> short message
and the processing of these messages fails, you can also throw a
<code>ProcessRequestException</code> instead of handle the failure. In this
case, this exception is forwarded to the underlying <a shape="rect"
class="external-link" href="http://code.google.com/p/jsmpp/";
rel="nofollow">JSMPP library</a> which will
return the included error code to the SMSC. This feature is useful to e.g.
instruct the SMSC to resend the short message at a later time. This could be
done with the following lines of code:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="BookComponentAppendix-Exceptionhandling.1">Exception
handling</h3><p>This component supports the general Camel exception handling
capabilities</p><p>When an error occurs sending a message with SubmitSm (the
default action), the org.apache.camel.component.smpp.SmppException is thrown
with a nested exception, org.jsmpp.extra.NegativeResponseException.  Call
NegativeResponseException.getCommandStatus() to obtain the exact SMPP negative
response code, the values are explained in the SMPP specification 3.4, section
5.1.3.<br clear="none"> <strong>Camel 2.8 onwards</strong>: When the SMPP
consumer receives a <code>DeliverSm</code> or <code>DataSm</code> short message
and the processing of these messages fails, you can also throw a
<code>ProcessRequestException</code> instead of handle the failure. In this
case, this exception is forwarded to the underlying <a shape="rect"
class="external-link" href="http://jsmpp.org"; rel="nofollow">JSMPP library</a>
which will return the incl
uded error code to the SMSC. This feature is useful to e.g. instruct the SMSC
to resend the short message at a later time. This could be done with the
following lines of 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[from("smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=consumer")
.doTry()
.to("bean:dao?method=updateSmsState")
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 Jan 20 15:22:30
2015
@@ -4126,11 +4126,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.rbtoc1421687952365 {padding: 0px;}
-div.rbtoc1421687952365 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1421687952365 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1421767173331 {padding: 0px;}
+div.rbtoc1421767173331 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1421767173331 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1421687952365">
+/*]]>*/</style></p><div class="toc-macro rbtoc1421767173331">
<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>
@@ -6316,11 +6316,11 @@ So we completed the last piece in the pi
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1421687954334 {padding: 0px;}
-div.rbtoc1421687954334 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1421687954334 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1421767177233 {padding: 0px;}
+div.rbtoc1421767177233 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1421767177233 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1421687954334">
+/*]]>*/</style><div class="toc-macro rbtoc1421767177233">
<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>
@@ -18946,11 +18946,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.rbtoc1421687970240 {padding: 0px;}
-div.rbtoc1421687970240 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1421687970240 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1421767228208 {padding: 0px;}
+div.rbtoc1421767228208 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1421767228208 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1421687970240">
+/*]]>*/</style></p><div class="toc-macro rbtoc1421767228208">
<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>
@@ -28891,7 +28891,7 @@ protected RouteBuilder createRouteBuilde
<p><strong>The Camel SIP component also ships with a Presence Agent that is
meant to be used for Testing and Demo purposes only.</strong> An example of
instantiating a Presence Agent is given above. </p>
<p>Note that the Presence Agent is set up as a user agent@localhost:5152 and
is capable of communicating with both Publisher as well as Subscriber. It has a
separate SIP stackName distinct from Publisher as well as Subscriber. While it
is set up as a Camel Consumer, it does not actually send any messages along the
route to the endpoint "mock:neverland".</p>
-<h2 id="BookInOnePage-SMPPComponent">SMPP Component</h2><p><strong>Available
as of Camel 2.2</strong></p><p>This component provides access to an SMSC (Short
Message Service Center) over the <a shape="rect" class="external-link"
href="http://smsforum.net/SMPP_v3_4_Issue1_2.zip"; rel="nofollow">SMPP</a>
protocol to send and receive SMS. The <a shape="rect" class="external-link"
href="http://code.google.com/p/jsmpp/"; rel="nofollow">JSMPP</a> library is used
for the protocol implementation.</p><p>The Camel component currently operates
as an <a shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/ESME"; rel="nofollow">ESME</a> (External
Short Messaging Entity) and not as an SMSC itself.</p><p>Starting with<strong>
Camel 2.9</strong> you are also able to execute ReplaceSm, QuerySm,
SubmitMulti, CancelSm and DataSm.</p><p>Maven users will need to add the
following dependency to their <code>pom.xml</code> for this component:</p><div
class="code panel pdl" style="border-w
idth: 1px;"><div class="codeContent panelContent pdl">
+<h2 id="BookInOnePage-SMPPComponent">SMPP Component</h2><p><strong>Available
as of Camel 2.2</strong></p><p>This component provides access to an SMSC (Short
Message Service Center) over the <a shape="rect" class="external-link"
href="http://smsforum.net/SMPP_v3_4_Issue1_2.zip"; rel="nofollow">SMPP</a>
protocol to send and receive SMS. The <a shape="rect" class="external-link"
href="http://jsmpp.org"; rel="nofollow">JSMPP</a> library is used for the
protocol implementation.</p><p>The Camel component currently operates as an <a
shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/ESME";
rel="nofollow">ESME</a> (External Short Messaging Entity) and not as an SMSC
itself.</p><p>Starting with<strong> Camel 2.9</strong> you are also able
to execute ReplaceSm, QuerySm, SubmitMulti, CancelSm and DataSm.</p><p>Maven
users will need to add the following dependency to their <code>pom.xml</code>
for this component:</p><div class="code panel pdl" style="border-width:
1px;"><di
v class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-smpp</artifactId>
@@ -28910,10 +28910,10 @@ smpps://[username@]hostname[:port][?opti
<p class="title">JSMPP library</p>
<span class="aui-icon icon-success">Icon</span>
<div class="message-content">
- <p>See the documentation of the <a shape="rect"
class="external-link" href="http://code.google.com/p/jsmpp/";
rel="nofollow">JSMPP Library</a> for more details about the underlying
library.</p>
+ <p>See the documentation of the <a shape="rect"
class="external-link" href="http://jsmpp.org"; rel="nofollow">JSMPP Library</a>
for more details about the underlying library.</p>
</div>
</div>
-<h3 id="BookInOnePage-Exceptionhandling.1">Exception handling</h3><p>This
component supports the general Camel exception handling capabilities</p><p>When
an error occurs sending a message with SubmitSm (the default action), the
org.apache.camel.component.smpp.SmppException is thrown with a nested
exception, org.jsmpp.extra.NegativeResponseException.  Call
NegativeResponseException.getCommandStatus() to obtain the exact SMPP negative
response code, the values are explained in the SMPP specification 3.4, section
5.1.3.<br clear="none"> <strong>Camel 2.8 onwards</strong>: When the SMPP
consumer receives a <code>DeliverSm</code> or <code>DataSm</code> short message
and the processing of these messages fails, you can also throw a
<code>ProcessRequestException</code> instead of handle the failure. In this
case, this exception is forwarded to the underlying <a shape="rect"
class="external-link" href="http://code.google.com/p/jsmpp/";
rel="nofollow">JSMPP library</a> which will return t
he included error code to the SMSC. This feature is useful to e.g. instruct
the SMSC to resend the short message at a later time. This could be done with
the following lines of code:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="BookInOnePage-Exceptionhandling.1">Exception handling</h3><p>This
component supports the general Camel exception handling capabilities</p><p>When
an error occurs sending a message with SubmitSm (the default action), the
org.apache.camel.component.smpp.SmppException is thrown with a nested
exception, org.jsmpp.extra.NegativeResponseException.  Call
NegativeResponseException.getCommandStatus() to obtain the exact SMPP negative
response code, the values are explained in the SMPP specification 3.4, section
5.1.3.<br clear="none"> <strong>Camel 2.8 onwards</strong>: When the SMPP
consumer receives a <code>DeliverSm</code> or <code>DataSm</code> short message
and the processing of these messages fails, you can also throw a
<code>ProcessRequestException</code> instead of handle the failure. In this
case, this exception is forwarded to the underlying <a shape="rect"
class="external-link" href="http://jsmpp.org"; rel="nofollow">JSMPP library</a>
which will return the included err
or code to the SMSC. This feature is useful to e.g. instruct the SMSC to
resend the short message at a later time. This could be done with the following
lines of 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[from("smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=consumer")
.doTry()
.to("bean:dao?method=updateSmsState")
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/smpp.html
==============================================================================
--- websites/production/camel/content/smpp.html (original)
+++ websites/production/camel/content/smpp.html Tue Jan 20 15:22:30 2015
@@ -85,7 +85,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="SMPP-SMPPComponent">SMPP
Component</h2><p><strong>Available as of Camel 2.2</strong></p><p>This
component provides access to an SMSC (Short Message Service Center) over the <a
shape="rect" class="external-link"
href="http://smsforum.net/SMPP_v3_4_Issue1_2.zip"; rel="nofollow">SMPP</a>
protocol to send and receive SMS. The <a shape="rect" class="external-link"
href="http://code.google.com/p/jsmpp/"; rel="nofollow">JSMPP</a> library is used
for the protocol implementation.</p><p>The Camel component currently operates
as an <a shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/ESME"; rel="nofollow">ESME</a> (External
Short Messaging Entity) and not as an SMSC itself.</p><p>Starting with<strong>
Camel 2.9</strong> you are also able to execute ReplaceSm, QuerySm,
SubmitMulti, CancelSm and DataSm.</p><p>Maven users will need to add the
following dependency to their <code>pom.xml</code> for this component:</p><div
class="co
de panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<div class="wiki-content maincontent"><h2 id="SMPP-SMPPComponent">SMPP
Component</h2><p><strong>Available as of Camel 2.2</strong></p><p>This
component provides access to an SMSC (Short Message Service Center) over the <a
shape="rect" class="external-link"
href="http://smsforum.net/SMPP_v3_4_Issue1_2.zip"; rel="nofollow">SMPP</a>
protocol to send and receive SMS. The <a shape="rect" class="external-link"
href="http://jsmpp.org"; rel="nofollow">JSMPP</a> library is used for the
protocol implementation.</p><p>The Camel component currently operates as an <a
shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/ESME";
rel="nofollow">ESME</a> (External Short Messaging Entity) and not as an SMSC
itself.</p><p>Starting with<strong> Camel 2.9</strong> you are also able
to execute ReplaceSm, QuerySm, SubmitMulti, CancelSm and DataSm.</p><p>Maven
users will need to add the following dependency to their <code>pom.xml</code>
for this component:</p><div class="code panel pdl" s
tyle="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-smpp</artifactId>
@@ -104,10 +104,10 @@ smpps://[username@]hostname[:port][?opti
<p class="title">JSMPP library</p>
<span class="aui-icon icon-success">Icon</span>
<div class="message-content">
- <p>See the documentation of the <a shape="rect"
class="external-link" href="http://code.google.com/p/jsmpp/";
rel="nofollow">JSMPP Library</a> for more details about the underlying
library.</p>
+ <p>See the documentation of the <a shape="rect"
class="external-link" href="http://jsmpp.org"; rel="nofollow">JSMPP Library</a>
for more details about the underlying library.</p>
</div>
</div>
-<h3 id="SMPP-Exceptionhandling">Exception handling</h3><p>This component
supports the general Camel exception handling capabilities</p><p>When an error
occurs sending a message with SubmitSm (the default action), the
org.apache.camel.component.smpp.SmppException is thrown with a nested
exception, org.jsmpp.extra.NegativeResponseException.  Call
NegativeResponseException.getCommandStatus() to obtain the exact SMPP negative
response code, the values are explained in the SMPP specification 3.4, section
5.1.3.<br clear="none"> <strong>Camel 2.8 onwards</strong>: When the SMPP
consumer receives a <code>DeliverSm</code> or <code>DataSm</code> short message
and the processing of these messages fails, you can also throw a
<code>ProcessRequestException</code> instead of handle the failure. In this
case, this exception is forwarded to the underlying <a shape="rect"
class="external-link" href="http://code.google.com/p/jsmpp/";
rel="nofollow">JSMPP library</a> which will return the included
error code to the SMSC. This feature is useful to e.g. instruct the SMSC to
resend the short message at a later time. This could be done with the following
lines of code:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<h3 id="SMPP-Exceptionhandling">Exception handling</h3><p>This component
supports the general Camel exception handling capabilities</p><p>When an error
occurs sending a message with SubmitSm (the default action), the
org.apache.camel.component.smpp.SmppException is thrown with a nested
exception, org.jsmpp.extra.NegativeResponseException.  Call
NegativeResponseException.getCommandStatus() to obtain the exact SMPP negative
response code, the values are explained in the SMPP specification 3.4, section
5.1.3.<br clear="none"> <strong>Camel 2.8 onwards</strong>: When the SMPP
consumer receives a <code>DeliverSm</code> or <code>DataSm</code> short message
and the processing of these messages fails, you can also throw a
<code>ProcessRequestException</code> instead of handle the failure. In this
case, this exception is forwarded to the underlying <a shape="rect"
class="external-link" href="http://jsmpp.org"; rel="nofollow">JSMPP library</a>
which will return the included error code to
the SMSC. This feature is useful to e.g. instruct the SMSC to resend the short
message at a later time. This could be done with the following lines of
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"><