Hi
Are you sure there is no more stacktrace details?
The caused exception is caught by Camel and recorded on the exchange at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:151)[camel-core-2.10-20120501.123310-101.jar:2.10-SNAPSHOT]
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 BeanProcessor.java
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 <soumya...@yahoo.com> 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:
> http://camel.465427.n5.nabble.com/Any-idea-why-this-simple-splitter-is-not-working-in-2-10-SNAPSHOT-tp5678336p5681688.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
