camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Any idea why this simple splitter is not working in 2.10-SNAPSHOT
Date Thu, 03 May 2012 12:11:41 GMT

Are you sure there is no more stacktrace details?

The caused exception is caught by Camel and recorded on the exchange at

Which is then logged by Tomcat later on. A bit odd it dont log the
caused exception.

As you use SNAPSHOT code, then feel free to modify
around line 151, and do a printStackTrace() etc on the caused
exception to see the cause.

Its related to Camel introspecting the bean, and some error occurs.

Also maybe you need a try .. catch when you use the Camel producer
template to log the caused exception.

On Wed, May 2, 2012 at 11:29 PM, soumya_sd <> wrote:
> I found a fix. However, I still don't completely understand it completely.
> My assumption was that when the splitResponse() method is invoked by Camel
> it is passed a GooglePlaceResponseObject. However, looks like that's not the
> case. Because when I changed the input to splitResponse() to an Exchange
> object and then get the GooglePlaceResponseObject from the "in body" it
> works. I even tried annotating the input to splitResponse(@Body
> GooglePlaceResponseobject) but it still didn't work.
>        public List<GooglePlaceVO> splitResponse(Exchange exchange) {
>                GooglePlaceResponseObject gpResponse =
> (GooglePlaceResponseObject)exchange.getIn().getBody();
> .....
> .....
> .....
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
CamelOne 2012 Conference, May 15-16, 2012:
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message