I logged a ticket: https://issues.apache.org/jira/browse/CAMEL-5963
Best,
Christian
On Sun, Jan 13, 2013 at 12:19 PM, Pontus Ullgren wrote:
> Agree, log and reject would be the best solution.
>
> // Pontus
>
> On Sun, Jan 13, 2013 at 12:01 PM, Christian Müller
> wrote:
> > Yes, it's possible t
Agree, log and reject would be the best solution.
// Pontus
On Sun, Jan 13, 2013 at 12:01 PM, Christian Müller
wrote:
> Yes, it's possible to share the jsmpp session, btw. we have to share it in
> this case (only one TRX connection is allowed).
> We could only log the received message, if no con
Yes, it's possible to share the jsmpp session, btw. we have to share it in
this case (only one TRX connection is allowed).
We could only log the received message, if no consumer route is defined.
But may be this is not suitable for most of our users.
We could also throw an exception at route/contex
Correction I was wrong on the direct endpoint restriction.
I was thinking about the log message that occurs when a exchange is
send to a direct endpoint without a consumer. So perhaps there is no
way to determine if there is a corresponding consuming endpoint at
start.
On Sun, Jan 13, 2013 at 11:
On Sat, Jan 12, 2013 at 6:47 PM, Christian Müller
wrote:
> 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 (a
