Re: request-reply with RabbitMQ and Camel

Hi Are you talking about this component? https://github.com/Bluelock/camel-spring-amqp If so them may raise an issue in their issue tracker about your issue, so they can see if they can improve this, or document how to do it etc. On Fri, Feb 20, 2015 at 10:54 PM, unleashed85 wrote: > Follow up:

Re: How to trap most specific exceptions?

If you have a copy of Camel in action book, read chapter 5, section 5.5 Use onException(Exception.class).onWhen and implement your own logic. On Fri, Feb 20, 2015 at 7:19 PM, toomanyedwards wrote: > Hi all, > I have situation like this. My route can throw the following exceptions: > > Appl

Re: Jpa Component: Difference between MaximumResults and MaxMessagesPerPoll parameters

Hi maximumResults is JPA specific and you should favor using that as the JPA allows to optimize for this. maxMessagesPerPoll is a general option in camel batch consumers that allows to limit the number of rows from the batch the consumer will process at this poll. Dont use the together, use the m

How to trap most specific exceptions?

Hi all, I have situation like this. My route can throw the following exceptions: ApplicationExceptionFoo->caused by IOException ApplicationExceptionBar->caused by IOException Generic IOException I want to be able to specifically trap ApplicationExceptionFoo, ApplicationExceptionBar and

Camel BeanIO catch and ignore InvalidRecordException

Hi, I'm trying to create a route which will read thousands of CSV records from a file, unmarshal using BeanIO, and perform further processing after that. During unmarshalling, if few records have validation error which results in InvalidRecordException, that record should be moved to an error file

Jpa Component: Difference between MaximumResults and MaxMessagesPerPoll parameters

Hi Guys, I'm using JPA Component and I'm not understanding the difference between these two parameters: maximumResults and maxMessagesPerPoll. If I set maximumResults=100 and maxMessagesPerPoll=20 it seems like on every polling my query retrieves 100 entities from database but only 20 of them are

Re: request-reply with RabbitMQ and Camel

Follow up: I finally got the request-reply working with the Camel-Spring-AMQP component. However, I did have to filter out some of the camel headers because they caused an "invalid value in table" error. -- View this message in context: http://camel.465427.n5.nabble.com/request-reply-with-Rab

Re: Assertion Problem - ExpectedBodiesReceived

All the expected bodies does is calls the equals method on your expected object against the object that actually came through. So if you told it to expect a list and you gave it a string, then it won’t pass. On 21 Feb 2015, at 8:34 am, Christian Weichselbaum wrote: > I just found out that the

Re: Assertion Problem - ExpectedBodiesReceived

I just found out that the problem was that the error message did mislead me. When I’m trying to get Strings through the route, expectedBodiesReceived works perfectly fine. If I do send List across the routes, then I’m struggling with the expectedBodiesReceived() method. On 20 Feb 2015, at 21:

Assertion Problem - ExpectedBodiesReceived

Hello, I’m having troubles with testing a camel route. Now I reduced the test and the route to almost nothing and was able to pinpoint the problem but am still struggling with finding a solution. The first snippet here does fail with following assertion problem: java.lang.AssertionError: mock

IBM MQ Issue because of Spring JMS Listener

HI, I am new to IBM MQ with Apache camel. below is my configuration * * my application is running in Spring Container. some time I am getting this below warning, hence My route is not working ( IBM MQ is not reading msg). for getting warning, Route is not working . *Exception

Re: dynamicRouter and redelivery

Can anyone help? Seems like redelivery with dynamicRouters doesn’t seem possible. On 18 Feb 2015, at 2:24 pm, Minh Tran wrote: > Hi > > I seem to be having an issue with redelivery for an endpoint being called > within a dynamic router in Camel 2.14.1. My endpoint is never called more > than

Re: Generating SoapFault from Spring DSL

Use instead of . The latter is also deprecated See also this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Fri, Feb 20, 2015 at 10:04 AM, L F wrote: > Hi > I'm trying to implement a webservice operation as a camel route (spring DSL), > and I'd like to generate

Generating SoapFault from Spring DSL

Hi I'm trying to implement a webservice operation as a camel route (spring DSL), and I'd  like to generate a soap fault from the route, when some condition is met. I created a route which should prepare this soap fault :                      

Re: snapshots broken?

Thanks for the fast build tip. I have 4 VMs that are all pulling 2.15-SNAPSHOT -- so if the remote repo is updated regularly that would be great. What's the snapshot update policy? Do I need to change the group id to use my own snapshot build of what is usually a remotely fetched snapshot? http: