useful information

Hello friend, I thought this information regarding my favourite stuff may be usefull for you too, just take a look here <http://present.caigu.ca/aeqctdu> Bests, sanjai -- View this message in context: http://camel.465427.n5.nabble.com/useful-information-tp5786368.html Sent fr

how you're doing?

Hi, Just wanted to say hi and ask how you're doing? I'm OK, you may read my latest article here Sincerely, san...@sanjai.org -- View this message in context: http://camel.465427.n5.nabble.com/how-you-re-doing-tp5783720.html Sent from the Came

news from me

Hello, I've got some interesting news for you, you're gonna be pleaseantly surprised. Read more here san...@sanjai.org -- View this message in context: http://camel.465427.n5.nabble.com/news-from-me-tp5783719.html Sent from the Camel - Users

Re: interesting things

Hi, I just read an article that you might be interested in, you won't regret, please read it here Bests, san...@sanjai.org -- View this message in context: http://camel.465427.n5.nabble.com/Re-interesting-things-tp5783225.html Sent from the Ca

i'm so excited

Hello! Just take a look at the info I just found, I'm so excited, check it out at Very truly yours, san...@sanjai.org -- View this message in context: http://camel.465427.n5.nabble.com/i-m-so-excited-tp5783087.html Sent from the Camel - Use

just for you

Hi, Look what they have for you, I guess it's worth reading, more info here san...@sanjai.org -- View this message in context: http://camel.465427.n5.nabble.com/just-for-you-tp5782683.html Sent from the Camel - Users mailing list archi

Re: Issue with recipientList and cxf in 2.8.0?

Awesome. Thanks Claus. Hopefully it will be fixed by the next release. -- View this message in context: http://camel.465427.n5.nabble.com/Issue-with-recipientList-and-cxf-in-2-8-0-tp4896788p4918821.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Issue with recipientList and cxf in 2.8.0?

Thanks Achim and Jiang for all the help. I think I'll just stay on 2.7.3 until this issue gets fixed in 2.8.x. I definitely need to beef up my unit tests to catch things like this in the future. -- View this message in context: http://camel.465427.n5.nabble.com/Issue-with-recipientList-and-cxf-

Re: Issue with recipientList and cxf in 2.8.0?

Thanks Achim. I'm glad I'm not the only once seeing this issue. I'm not sure I understand how I would use RequestConext to send to multiple cxf endpoints. Do you have an example on how to do this? Thanks Sanjai -- View this message in context: http://camel.465427.n5.nabble

Issue with recipientList and cxf in 2.8.0?

Hello all, I have a route that had been working fine in our production system. The route is fairly basic. It simply reads messages of a JMS queue, does some processing on the message and then sends the message to multiple cxf endpoints. The sending to multiple endpoints is done by using recipie

Re: How to consume from multiple JMS queues?

Thanks Claus. I'll try that. -- View this message in context: http://camel.465427.n5.nabble.com/How-to-consume-from-multiple-JMS-queues-tp4857383p4857785.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: How to consume from multiple JMS queues?

Each queue contains data for a separate customer. Customers can pull data from their queue indirectly via a web service call they make to us which pulls from the company queues and return the resulting messages. However, there are some customers who want us to "push" data to them by calling thei

How to consume from multiple JMS queues?

Hello all, I need a route to consume from multiple JMS (not activemq) queues. It seems that the JMS Component does not have a direct way to do this. To add to the complexity, the queues that the route reads from can change during runtime. Can someone guide me how this can be done within Camel?

Re: onexception behavior change from 2.5 to 2.6

A little more on this. The behaviour is not quite as my original post describes. I have another onexception clause which picks up all other exceptions as shown at the end of this post. It turns out that when redelivery fails from the previous on exception clause, Camel thows a CamelException w

onexception behavior change from 2.5 to 2.6

Hello all, There seems to have been some change in the way onexception behaves from 2.5 to 2.6 an onwards. I believe the behaviour in 2.5 was correct. I have onexception set up as follows (in spring): java.net.SocketTimeoutExcept