The thorny issue with the TRX mode is that it uses a conversational
pattern, not really quite supported/modeled well.
Since the Endpoint is the one creating the Producers and Consumers, it
could be used to share the conversation state. I believe a cleaner
solution would be to model a Conversation and have consumers and
producers join it. But a quick and dirty solution would do too.
Cheers,
Hadrian
On 06/27/2013 05:28 PM, Christian Müller wrote:
From the spec:
5.2.3
The system_type parameter is used to categorize the type of ESME that is
binding to the SMSC.
Examples include “VMS” (voice mail system) and “OTA” (over-the-air
activation system).
Specification of the system_type is optional - some SMSC’s may not require
ESME’s to provide
this detail. In this case, the ESME can set the system_type to NULL.
Best,
Christian
-----------------
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Wed, Jun 26, 2013 at 8:08 AM, sash_...@yahoo.com <sash_...@yahoo.com>wrote:
What is the use of "systemType" paramter ? I don't see any differentiation
in the code based on this parameter . Am I missing something ?
The possible values are "producer" , "consumer"
-----
~Sandeep
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-smpp-in-trx-mode-tp5724608p5734784.html
Sent from the Camel - Users mailing list archive at Nabble.com.
