Author: buildbot
Date: Thu May 30 22:20:51 2013
New Revision: 863805
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/camel-2120-release.html
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 Thu May 30
22:20:51 2013
@@ -15714,13 +15714,13 @@ smpp:<span class="code-comment">//smppcl
<div class="confluenceTableSmall"><div class="table-wrap">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppDestAddr</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>List</tt>/<tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>only for SubmitSm,
SubmitMulti, CancelSm and DataSm</b> Defines the destination SME address(es).
For mobile terminated messages, this is the directory number of the recipient
MS. Is must be a <tt>List<String></tt> for SubmitMulti and a
<tt>String</tt> otherwise. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppDestAddrTon</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>only for SubmitSm, SubmitMulti, CancelS
m and DataSm</b> Defines the type of number (TON) to be used in the SME
destination address parameters. Use the <tt>sourceAddrTon</tt> URI option
values defined above. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppDestAddrNpi</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>only for SubmitSm, SubmitMulti, CancelSm
and DataSm</b> Defines the numeric plan indicator (NPI) to be used in the SME
destination address parameters. Use the URI option <tt>sourceAddrNpi</tt>
values defined above.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppSourceAddr</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Defines the address of SME (Short Message
Entity) which originated this message. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppSourceAdd
rTon</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> Defines the type of
number (TON) to be used in the SME originator address parameters. Use the
<tt>sourceAddrTon</tt> URI option values defined above. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelSmppSourceAddrNpi</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Defines the numeric plan
indicator (NPI) to be used in the SME originator address parameters. Use the
URI option <tt>sourceAddrNpi</tt> values defined above.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelSmppServiceType</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The service type parameter can be
used to indicate the SMS Application service associated with the message.
Use the URI option <tt>serviceType</tt> settings above.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppRegisteredDelivery</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>only for SubmitSm, ReplaceSm, SubmitMulti and
DataSm</b> Is used to request an SMSC delivery receipt and/or SME originated
acknowledgements. Use the URI option <tt>registeredDelivery</tt> settings
above. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppPriorityFlag</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>only for SubmitSm and SubmitMulti</b> Allows the
originating SME to assign a priority level to the short message. Use the URI
option <tt>priorityFlag</tt> settings above.</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppScheduleDeliveryTime</tt> </td><t
d colspan="1" rowspan="1" class="confluenceTd"> <tt>Date</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>only for SubmitSm, SubmitMulti
and ReplaceSm</b> This parameter specifies the scheduled time at which the
message delivery should be first attempted. It defines either the absolute date
and time or relative time from the current SMSC time at which delivery of this
message will be attempted by the SMSC. It can be specified in either absolute
time format or relative time format. The encoding of a time format is specified
in chapter 7.1.1. in the smpp specification v3.4. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppValidityPeriod</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt>/<tt>Date</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>only for SubmitSm,
SubmitMulti and ReplaceSm</b> The validity period parameter indicates the SMSC
expiration time, after which the message should be discard
ed if not delivered to the destination. If it's provided as <tt>Date</tt>,
it's interpreted as absolute time. <b>Camel 2.9.1 onwards:</b> It can be
defined in absolute time format or relative time format if you provide it as
<tt>String</tt> as specified in chapter 7.1.1 in the smpp specification v3.4.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppReplaceIfPresentFlag</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>only for SubmitSm and SubmitMulti</b> The replace if
present flag parameter is used to request the SMSC to replace a previously
submitted message, that is still pending delivery. The SMSC will replace an
existing message provided that the source address, destination address and
service type match the same fields in the new message. The following values are
defined: <br clear="none" class="atl-forced-newline">
<tt>0</tt>: Don't replace<br clear="none" class="atl-forced-newline">
-<tt>1</tt>: Replace </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppAlphabet</tt> / <tt>CamelSmppDataCoding</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5</b> <b>For SubmitSm,
SubmitMulti and ReplaceSm</b> (Prior to <b>Camel 2.9</b> use
<tt>CamelSmppDataCoding</tt> instead of <tt>CamelSmppAlphabet</tt>.) The data
coding according to the SMPP 3.4 specification, section 5.2.19. Use the URI
option <tt>alphabet</tt> settings above. </td></tr></tbody></table>
+<tt>1</tt>: Replace </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppAlphabet</tt> / <tt>CamelSmppDataCoding</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5</b> <b>For SubmitSm,
SubmitMulti and ReplaceSm</b> (Prior to <b>Camel 2.9</b> use
<tt>CamelSmppDataCoding</tt> instead of <tt>CamelSmppAlphabet</tt>.) The data
coding according to the SMPP 3.4 specification, section 5.2.19. Use the URI
option <tt>alphabet</tt> settings above. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppOptionalParameters</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>Map<String,
String></tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel
2.10.5 and 2.11.1 onwards and only for SubmitSm, SubmitMulti and DataSm</b> The
optional parameters send back by the SMSC. </td></tr></tbody></table>
</div>
</div>
<p>The following message headers are used by the SMPP producer to set the
response from the SMSC in the message header</p>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>List<String></tt>/<tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The id to identify the submitted
short message(s) for later use. <b>From Camel 2.9.0</b>: In case of a
ReplaceSm, QuerySm, CancelSm and DataSm this header vaule is a <tt>String</tt>.
In case of a SubmitSm or SubmitMultiSm this header vaule is a
<tt>List<String></tt>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppSentMessageCount</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onward
s only for SubmitSm and SubmitMultiSm</b> The total number of messages which
has been sent. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppError</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>Map<String, List<Map<String, Object>>></tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onwards only
for SubmitMultiSm</b> The errors which occurred by sending the short message(s)
the form <tt>Map<String, List<Map<String, Object>>></tt>
(messageID : (destAddr : address, error : errorCode)).
</td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>List<String></tt>/<tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The id to identify the submitted
short message(s) for later use. <b>From Camel 2.9.0</b>: In case of a
ReplaceSm, QuerySm, CancelSm and DataSm this header vaule is a <tt>String</tt>.
In case of a SubmitSm or SubmitMultiSm this header vaule is a
<tt>List<String></tt>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppSentMessageCount</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onward
s only for SubmitSm and SubmitMultiSm</b> The total number of messages which
has been sent. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppError</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>Map<String, List<Map<String, Object>>></tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onwards only
for SubmitMultiSm</b> The errors which occurred by sending the short message(s)
the form <tt>Map<String, List<Map<String, Object>>></tt>
(messageID : (destAddr : address, error : errorCode)). </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppOptionalParameters</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Map<String, String></tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>From Camel 2.11.1 onwards only for
DataSm</b> The optinal parameters which are returned from the SMSC by sending
the message. </td></tr></tbody
></table>
</div>
</div>
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 Thu May 30 22:20:51
2013
@@ -36779,13 +36779,13 @@ smpp:<span class="code-comment">//smppcl
<div class="confluenceTableSmall"><div class="table-wrap">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppDestAddr</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>List</tt>/<tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>only for SubmitSm,
SubmitMulti, CancelSm and DataSm</b> Defines the destination SME address(es).
For mobile terminated messages, this is the directory number of the recipient
MS. Is must be a <tt>List<String></tt> for SubmitMulti and a
<tt>String</tt> otherwise. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppDestAddrTon</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>only for SubmitSm, SubmitMulti, CancelS
m and DataSm</b> Defines the type of number (TON) to be used in the SME
destination address parameters. Use the <tt>sourceAddrTon</tt> URI option
values defined above. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppDestAddrNpi</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>only for SubmitSm, SubmitMulti, CancelSm
and DataSm</b> Defines the numeric plan indicator (NPI) to be used in the SME
destination address parameters. Use the URI option <tt>sourceAddrNpi</tt>
values defined above.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppSourceAddr</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Defines the address of SME (Short Message
Entity) which originated this message. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppSourceAdd
rTon</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> Defines the type of
number (TON) to be used in the SME originator address parameters. Use the
<tt>sourceAddrTon</tt> URI option values defined above. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelSmppSourceAddrNpi</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Defines the numeric plan
indicator (NPI) to be used in the SME originator address parameters. Use the
URI option <tt>sourceAddrNpi</tt> values defined above.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelSmppServiceType</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The service type parameter can be
used to indicate the SMS Application service associated with the message.
Use the URI option <tt>serviceType</tt> settings above.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppRegisteredDelivery</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>only for SubmitSm, ReplaceSm, SubmitMulti and
DataSm</b> Is used to request an SMSC delivery receipt and/or SME originated
acknowledgements. Use the URI option <tt>registeredDelivery</tt> settings
above. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppPriorityFlag</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>only for SubmitSm and SubmitMulti</b> Allows the
originating SME to assign a priority level to the short message. Use the URI
option <tt>priorityFlag</tt> settings above.</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppScheduleDeliveryTime</tt> </td><t
d colspan="1" rowspan="1" class="confluenceTd"> <tt>Date</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>only for SubmitSm, SubmitMulti
and ReplaceSm</b> This parameter specifies the scheduled time at which the
message delivery should be first attempted. It defines either the absolute date
and time or relative time from the current SMSC time at which delivery of this
message will be attempted by the SMSC. It can be specified in either absolute
time format or relative time format. The encoding of a time format is specified
in chapter 7.1.1. in the smpp specification v3.4. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppValidityPeriod</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt>/<tt>Date</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>only for SubmitSm,
SubmitMulti and ReplaceSm</b> The validity period parameter indicates the SMSC
expiration time, after which the message should be discard
ed if not delivered to the destination. If it's provided as <tt>Date</tt>,
it's interpreted as absolute time. <b>Camel 2.9.1 onwards:</b> It can be
defined in absolute time format or relative time format if you provide it as
<tt>String</tt> as specified in chapter 7.1.1 in the smpp specification v3.4.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppReplaceIfPresentFlag</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>only for SubmitSm and SubmitMulti</b> The replace if
present flag parameter is used to request the SMSC to replace a previously
submitted message, that is still pending delivery. The SMSC will replace an
existing message provided that the source address, destination address and
service type match the same fields in the new message. The following values are
defined: <br clear="none" class="atl-forced-newline">
<tt>0</tt>: Don't replace<br clear="none" class="atl-forced-newline">
-<tt>1</tt>: Replace </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppAlphabet</tt> / <tt>CamelSmppDataCoding</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5</b> <b>For SubmitSm,
SubmitMulti and ReplaceSm</b> (Prior to <b>Camel 2.9</b> use
<tt>CamelSmppDataCoding</tt> instead of <tt>CamelSmppAlphabet</tt>.) The data
coding according to the SMPP 3.4 specification, section 5.2.19. Use the URI
option <tt>alphabet</tt> settings above. </td></tr></tbody></table>
+<tt>1</tt>: Replace </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppAlphabet</tt> / <tt>CamelSmppDataCoding</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5</b> <b>For SubmitSm,
SubmitMulti and ReplaceSm</b> (Prior to <b>Camel 2.9</b> use
<tt>CamelSmppDataCoding</tt> instead of <tt>CamelSmppAlphabet</tt>.) The data
coding according to the SMPP 3.4 specification, section 5.2.19. Use the URI
option <tt>alphabet</tt> settings above. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppOptionalParameters</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>Map<String,
String></tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel
2.10.5 and 2.11.1 onwards and only for SubmitSm, SubmitMulti and DataSm</b> The
optional parameters send back by the SMSC. </td></tr></tbody></table>
</div>
</div>
<p>The following message headers are used by the SMPP producer to set the
response from the SMSC in the message header</p>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>List<String></tt>/<tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The id to identify the submitted
short message(s) for later use. <b>From Camel 2.9.0</b>: In case of a
ReplaceSm, QuerySm, CancelSm and DataSm this header vaule is a <tt>String</tt>.
In case of a SubmitSm or SubmitMultiSm this header vaule is a
<tt>List<String></tt>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppSentMessageCount</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onward
s only for SubmitSm and SubmitMultiSm</b> The total number of messages which
has been sent. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppError</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>Map<String, List<Map<String, Object>>></tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onwards only
for SubmitMultiSm</b> The errors which occurred by sending the short message(s)
the form <tt>Map<String, List<Map<String, Object>>></tt>
(messageID : (destAddr : address, error : errorCode)).
</td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>List<String></tt>/<tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The id to identify the submitted
short message(s) for later use. <b>From Camel 2.9.0</b>: In case of a
ReplaceSm, QuerySm, CancelSm and DataSm this header vaule is a <tt>String</tt>.
In case of a SubmitSm or SubmitMultiSm this header vaule is a
<tt>List<String></tt>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppSentMessageCount</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onward
s only for SubmitSm and SubmitMultiSm</b> The total number of messages which
has been sent. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppError</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>Map<String, List<Map<String, Object>>></tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onwards only
for SubmitMultiSm</b> The errors which occurred by sending the short message(s)
the form <tt>Map<String, List<Map<String, Object>>></tt>
(messageID : (destAddr : address, error : errorCode)). </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppOptionalParameters</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Map<String, String></tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>From Camel 2.11.1 onwards only for
DataSm</b> The optinal parameters which are returned from the SMSC by sending
the message. </td></tr></tbody
></table>
</div>
</div>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-2120-release.html
==============================================================================
--- websites/production/camel/content/camel-2120-release.html (original)
+++ websites/production/camel/content/camel-2120-release.html Thu May 30
22:20:51 2013
@@ -84,7 +84,7 @@
<p>Welcome to the 2.12.0 release which approx XXX issues resolved (new
features, improvements and bug fixes such as...)</p>
-<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint
Annotations">Endpoint Annotations</a> along with automatically created HTML
documentation for the endpoint parameters; this makes it easier for component
developers to add a few refactoring-safe annotations to their Endpoint or
Consumer implementations and, (along with javadoc comments on the field or
setter method), get nice user documentation on how to use the endpoint for
free.</li><li><a shape="rect" href="componentconfiguration.html"
title="ComponentConfiguration">ComponentConfiguration</a> API provides a handy
API for tools developers to introspect on a Component to find all the possible
parameters, their types and any extra annotations (like Bean Validation
Annotations) to be able to create/edit endpoints or URI strings so that tools
can generate nicer UIs for configuring endpoints than just letting folks edit
Strings.</li><li><a shape="rect" href="endpointcompleter.html"
title="EndpointCompleter
">EndpointCompleter</a> API provides a hook so that command line tools (like
<a shape="rect" class="external-link"
href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html";>Karaf's
shell</a>), IDEs and web tools can get (bash tab like) auto-completion on
endpoint paths (such as file or directory names, message queue names, database
table names) when creating or using new endpoints</li><li>Reduced stack-frames
in use during routing, that also makes Camel's stack traces being logged much
less verbose. This also allows people to easier debug the internals of Camel as
less <tt>AsyncCallback</tt> callbacks are in use during routing.</li><li><a
shape="rect" href="spring-web-services.html" title="Spring Web Services">Spring
Web Services</a> now supports setting/receiving SOAP headers more easily using
a header on the Camel <a shape="rect" href="message.html"
title="Message">Message</a>.</li><li>Evaluating <a shape="rect"
href="groovy.html" title="Groovy">Gro
ovy</a> expressions is faster as we cache the compiled scripts.</li><li>Added
<tt>base64</tt> option to <a shape="rect" href="shiro-security.html"
title="Shiro Security">Shiro Security</a> to allow transferring security token
over <a shape="rect" href="jms.html" title="JMS">JMS</a> and other transports
as base64 encoded representation.</li><li>Made it easier to use <a shape="rect"
href="shiro-security.html" title="Shiro Security">Shiro Security</a> as the
credentials can be provided in headers, when sending a message to a secured
route.</li><li><a shape="rect" href="bindy.html" title="Bindy">Bindy</a> now
supports enums.</li><li>Added new <a shape="rect" href="backlogdebugger.html"
title="BacklogDebugger">BacklogDebugger</a> to perform live debugging of
messages during routing. The <a shape="rect" href="backlogdebugger.html"
title="BacklogDebugger">BacklogDebugger</a> has JMX API allows tooling to
control the debugger.</li><li>While using the <a shape="rect" class="external-
link" href="http://xircles.codehaus.org/projects/jackson";
rel="nofollow">Jackson library</a> through the <a shape="rect" href="json.html"
title="JSON">JSON</a> Dataformat there's now a <tt>jsonView</tt> attribute you
could make use of directly inside the <a shape="rect" href="dsl.html"
title="DSL">DSL</a> itself.</li></ul>
+<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint
Annotations">Endpoint Annotations</a> along with automatically created HTML
documentation for the endpoint parameters; this makes it easier for component
developers to add a few refactoring-safe annotations to their Endpoint or
Consumer implementations and, (along with javadoc comments on the field or
setter method), get nice user documentation on how to use the endpoint for
free.</li><li><a shape="rect" href="componentconfiguration.html"
title="ComponentConfiguration">ComponentConfiguration</a> API provides a handy
API for tools developers to introspect on a Component to find all the possible
parameters, their types and any extra annotations (like Bean Validation
Annotations) to be able to create/edit endpoints or URI strings so that tools
can generate nicer UIs for configuring endpoints than just letting folks edit
Strings.</li><li><a shape="rect" href="endpointcompleter.html"
title="EndpointCompleter
">EndpointCompleter</a> API provides a hook so that command line tools (like
<a shape="rect" class="external-link"
href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html";>Karaf's
shell</a>), IDEs and web tools can get (bash tab like) auto-completion on
endpoint paths (such as file or directory names, message queue names, database
table names) when creating or using new endpoints</li><li>Reduced stack-frames
in use during routing, that also makes Camel's stack traces being logged much
less verbose. This also allows people to easier debug the internals of Camel as
less <tt>AsyncCallback</tt> callbacks are in use during routing.</li><li><a
shape="rect" href="spring-web-services.html" title="Spring Web Services">Spring
Web Services</a> now supports setting/receiving SOAP headers more easily using
a header on the Camel <a shape="rect" href="message.html"
title="Message">Message</a>.</li><li>Evaluating <a shape="rect"
href="groovy.html" title="Groovy">Gro
ovy</a> expressions is faster as we cache the compiled scripts.</li><li>Added
<tt>base64</tt> option to <a shape="rect" href="shiro-security.html"
title="Shiro Security">Shiro Security</a> to allow transferring security token
over <a shape="rect" href="jms.html" title="JMS">JMS</a> and other transports
as base64 encoded representation.</li><li>Made it easier to use <a shape="rect"
href="shiro-security.html" title="Shiro Security">Shiro Security</a> as the
credentials can be provided in headers, when sending a message to a secured
route.</li><li><a shape="rect" href="bindy.html" title="Bindy">Bindy</a> now
supports enums.</li><li>Added new <a shape="rect" href="backlogdebugger.html"
title="BacklogDebugger">BacklogDebugger</a> to perform live debugging of
messages during routing. The <a shape="rect" href="backlogdebugger.html"
title="BacklogDebugger">BacklogDebugger</a> has JMX API allows tooling to
control the debugger.</li><li>While using the <a shape="rect" class="external-
link" href="http://xircles.codehaus.org/projects/jackson";
rel="nofollow">Jackson library</a> through the <a shape="rect" href="json.html"
title="JSON">JSON</a> Dataformat there's now a <tt>jsonView</tt> attribute you
could make use of directly inside the <a shape="rect" href="dsl.html"
title="DSL">DSL</a> itself.</li><li><a shape="rect" href="smpp.html"
title="SMPP">SMPP</a> now supports optional parameters in all commands where
they are possible.</li></ul>
<h3><a shape="rect" name="Camel2.12.0Release-FixedIssues"></a>Fixed Issues</h3>
Modified: websites/production/camel/content/smpp.html
==============================================================================
--- websites/production/camel/content/smpp.html (original)
+++ websites/production/camel/content/smpp.html Thu May 30 22:20:51 2013
@@ -171,13 +171,13 @@ smpp:<span class="code-comment">//smppcl
<div class="confluenceTableSmall"><div class="table-wrap">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppDestAddr</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>List</tt>/<tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>only for SubmitSm,
SubmitMulti, CancelSm and DataSm</b> Defines the destination SME address(es).
For mobile terminated messages, this is the directory number of the recipient
MS. Is must be a <tt>List<String></tt> for SubmitMulti and a
<tt>String</tt> otherwise. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppDestAddrTon</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>only for SubmitSm, SubmitMulti, CancelS
m and DataSm</b> Defines the type of number (TON) to be used in the SME
destination address parameters. Use the <tt>sourceAddrTon</tt> URI option
values defined above. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppDestAddrNpi</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>only for SubmitSm, SubmitMulti, CancelSm
and DataSm</b> Defines the numeric plan indicator (NPI) to be used in the SME
destination address parameters. Use the URI option <tt>sourceAddrNpi</tt>
values defined above.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppSourceAddr</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Defines the address of SME (Short Message
Entity) which originated this message. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppSourceAdd
rTon</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> Defines the type of
number (TON) to be used in the SME originator address parameters. Use the
<tt>sourceAddrTon</tt> URI option values defined above. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelSmppSourceAddrNpi</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Defines the numeric plan
indicator (NPI) to be used in the SME originator address parameters. Use the
URI option <tt>sourceAddrNpi</tt> values defined above.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelSmppServiceType</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The service type parameter can be
used to indicate the SMS Application service associated with the message.
Use the URI option <tt>serviceType</tt> settings above.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppRegisteredDelivery</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>only for SubmitSm, ReplaceSm, SubmitMulti and
DataSm</b> Is used to request an SMSC delivery receipt and/or SME originated
acknowledgements. Use the URI option <tt>registeredDelivery</tt> settings
above. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppPriorityFlag</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>only for SubmitSm and SubmitMulti</b> Allows the
originating SME to assign a priority level to the short message. Use the URI
option <tt>priorityFlag</tt> settings above.</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppScheduleDeliveryTime</tt> </td><t
d colspan="1" rowspan="1" class="confluenceTd"> <tt>Date</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>only for SubmitSm, SubmitMulti
and ReplaceSm</b> This parameter specifies the scheduled time at which the
message delivery should be first attempted. It defines either the absolute date
and time or relative time from the current SMSC time at which delivery of this
message will be attempted by the SMSC. It can be specified in either absolute
time format or relative time format. The encoding of a time format is specified
in chapter 7.1.1. in the smpp specification v3.4. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppValidityPeriod</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt>/<tt>Date</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>only for SubmitSm,
SubmitMulti and ReplaceSm</b> The validity period parameter indicates the SMSC
expiration time, after which the message should be discard
ed if not delivered to the destination. If it's provided as <tt>Date</tt>,
it's interpreted as absolute time. <b>Camel 2.9.1 onwards:</b> It can be
defined in absolute time format or relative time format if you provide it as
<tt>String</tt> as specified in chapter 7.1.1 in the smpp specification v3.4.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppReplaceIfPresentFlag</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Byte</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>only for SubmitSm and SubmitMulti</b> The replace if
present flag parameter is used to request the SMSC to replace a previously
submitted message, that is still pending delivery. The SMSC will replace an
existing message provided that the source address, destination address and
service type match the same fields in the new message. The following values are
defined: <br clear="none" class="atl-forced-newline">
<tt>0</tt>: Don't replace<br clear="none" class="atl-forced-newline">
-<tt>1</tt>: Replace </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppAlphabet</tt> / <tt>CamelSmppDataCoding</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5</b> <b>For SubmitSm,
SubmitMulti and ReplaceSm</b> (Prior to <b>Camel 2.9</b> use
<tt>CamelSmppDataCoding</tt> instead of <tt>CamelSmppAlphabet</tt>.) The data
coding according to the SMPP 3.4 specification, section 5.2.19. Use the URI
option <tt>alphabet</tt> settings above. </td></tr></tbody></table>
+<tt>1</tt>: Replace </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppAlphabet</tt> / <tt>CamelSmppDataCoding</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Byte</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5</b> <b>For SubmitSm,
SubmitMulti and ReplaceSm</b> (Prior to <b>Camel 2.9</b> use
<tt>CamelSmppDataCoding</tt> instead of <tt>CamelSmppAlphabet</tt>.) The data
coding according to the SMPP 3.4 specification, section 5.2.19. Use the URI
option <tt>alphabet</tt> settings above. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>CamelSmppOptionalParameters</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>Map<String,
String></tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel
2.10.5 and 2.11.1 onwards and only for SubmitSm, SubmitMulti and DataSm</b> The
optional parameters send back by the SMSC. </td></tr></tbody></table>
</div>
</div>
<p>The following message headers are used by the SMPP producer to set the
response from the SMSC in the message header</p>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>List<String></tt>/<tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The id to identify the submitted
short message(s) for later use. <b>From Camel 2.9.0</b>: In case of a
ReplaceSm, QuerySm, CancelSm and DataSm this header vaule is a <tt>String</tt>.
In case of a SubmitSm or SubmitMultiSm this header vaule is a
<tt>List<String></tt>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppSentMessageCount</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onward
s only for SubmitSm and SubmitMultiSm</b> The total number of messages which
has been sent. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppError</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>Map<String, List<Map<String, Object>>></tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onwards only
for SubmitMultiSm</b> The errors which occurred by sending the short message(s)
the form <tt>Map<String, List<Map<String, Object>>></tt>
(messageID : (destAddr : address, error : errorCode)).
</td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>List<String></tt>/<tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The id to identify the submitted
short message(s) for later use. <b>From Camel 2.9.0</b>: In case of a
ReplaceSm, QuerySm, CancelSm and DataSm this header vaule is a <tt>String</tt>.
In case of a SubmitSm or SubmitMultiSm this header vaule is a
<tt>List<String></tt>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelSmppSentMessageCount</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onward
s only for SubmitSm and SubmitMultiSm</b> The total number of messages which
has been sent. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppError</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>Map<String, List<Map<String, Object>>></tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>From Camel 2.9 onwards only
for SubmitMultiSm</b> The errors which occurred by sending the short message(s)
the form <tt>Map<String, List<Map<String, Object>>></tt>
(messageID : (destAddr : address, error : errorCode)). </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelSmppOptionalParameters</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Map<String, String></tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>From Camel 2.11.1 onwards only for
DataSm</b> The optinal parameters which are returned from the SMSC by sending
the message. </td></tr></tbody
></table>
</div>
</div>
