Camel SMPP component question

Dears, I am using Camel SMPP component for Deliver SM and Submit SM. Submit SM is working fine. But whenever multiple Deliver SM(MO - Mobile Originated) requests comes to SMPP End Point then all of them are not processed by camel exchange as some of them got discarded as they did not processed by

Camel.trunk.notest - Build # 1898 - Still Failing

The Apache Jenkins build system has built Camel.trunk.notest (build #1898) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/1898/ to view the results.

camel pull request: CAMEL-5829

Github user NersesAM closed the pull request at: https://github.com/apache/camel/pull/22

Re: The read-only Git mirror for Apache Camel not being updated on GitHub...

It's cool. I can see the http://github.com/apache/camel is shown the latest changes on camel master branch. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot

Re: FW: The read-only Git mirror for Apache Camel not being updated on GitHub...

Hi Just to let you know that our read-only mirror on GitHub is synced again: https://issues.apache.org/jira/browse/INFRA-6248 Babak Babak Vahdat wrote > FYI. > > Babak > > Am 09.05.13 10:27 schrieb "Babak Vahdat" unter > < > babak.vahdat@ > >: > >> >>Thanks for your reply. I've already ra

Re: [HEADS UP] - Camel routing engine dumps message history when exhausted exception is logged

Hi I ponder with the idea of also dumping the Exchange body + headers as well. With an option to turn this on|off. Then by default when you develop with Camel and any exception occurs which is not expected or handled by onException etc we log with a nice to see "what is going on" with "my data" fr

Re: Feature request: support setOutBody in XML definitions

I wasn't able to find the issue you're mentioning in Jira, by any change do you have the issue number ? Thanks a lot, Antoine. 2013/6/7 Claus Ibsen > Because handles this internally as well the Camel routing engine. > > And there was a bug in Camel, so when you had short routes, like > > fro

Re: Camel always sending MQRFH2 headers to target WebsphereMQ queue.

Solved my problem by using the following snapshot at camel website... initially i was trying at router level ..then i moved to component level which seems logical. Register component with camel context and then start the router. A workaround is to use a custom DestinationResolver: JmsComponent w

Re: Feature request: support setOutBody in XML definitions

Because handles this internally as well the Camel routing engine. And there was a bug in Camel, so when you had short routes, like from X setBody This is fixed in recent/upcoming releases (cant remember exact when) Also see this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exc

Re: Feature request: support setOutBody in XML definitions

Hi, Why are they deprecated ? I want to create a restlet consumer (see [1]) using XML, and the documentation states that the response should be defined in the OUT message. As of today I was the following sample code http://localhost:/hello/{id}"/> Hello