camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject Re: camel-smpp in trx mode
Date Sat, 12 Jan 2013 17:47:35 GMT
The smslib model is a bit different. The smslib camel consumer pull the
short messages for the SMSC. And only if a consumer is defined (
from("smslib://...") ).
In the smpp Camel component, the SMPP library push the short messages (and
delivery receipt messages) to the client if the client is connected in the
TRX mode.
Assume there is only one producer ( to("smpp://...") ) defined and no
consumer. The SMPP library push the message to the client. Because there is
no Camel consumer, there is no route which can consume/handle/process/...
this message. What is a good/acceptable behavior in this case?


On Thu, Jan 10, 2013 at 1:37 PM, Alex Anderson <>wrote:

> On 4 January 2013 17:26, Christian Müller <>
> wrote:
> > I think we don't have another camel component where the endpoint is a
> > consumer and producer. I'm not sure how/if it works or if we hit problems
> > in other areas (exception handling, ...).
> We do this for the camel-smslib component.  The endpoint represents a
> serial connection to an SMS modem, and therefore must deal with either
> sending or receiving of messages or both.  I have no idea if this is a
> recommended approach from camel perspective, but it works for us.  My
> interpretation of the camel doc was that returning `true` from
> Endpoint.isSingleton() should allow for one Endpoint per URI, but
> multiple consumers/producers tied to the Endpoint.
> You can see example at


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message