On Thu, May 3, 2012 at 2:37 PM, soumya_sd <soumya...@yahoo.com> wrote: > Thank you for responding back. My understanding is that Camel should > automatically convert and pass the correct object type to my custom splitter > method. Is this correct ? >
Yes it will. And its much likely that the process in Camel that introspect the bean fails for some unknown reason, and that isnt logged. > > Claus Ibsen-2 wrote >> >> Hi >> >> Are you sure there is no more stacktrace details? >> >> >> > Yes. This is the only stacktrace that I see on tomcat logs. > > > Claus Ibsen-2 wrote >> >> >> 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. >> >> > > I thought of doing that but for some reason I cannot make maven to download > the SNAPSHOT code along with the build jar. I'm assuming I need to manually > download it and then build it locally and tell maven to pick it up the local > version instead of the SNAPSHOT version. Or is there an easier way ? > Yes you would need to build from source. There is details here http://camel.apache.org/building.html Then from the source root, do a normal build without tests. Then new SNAPSHOT files is compiled and installed in your local m2 repo. > > > Claus Ibsen-2 wrote >> >> >> Also maybe you need a try .. catch when you use the Camel producer >> template to log the caused exception. >> > > I added the following to my producer template but it still doesn't log any > exceptions. > try > { > ProducerTemplate template = > ctxAware.getCamelContext().createProducerTemplate(); > template.request("direct:start", new MyCustomProcessor()); > }catch(Exception e) > { > e.printStackTrace(); > } > > Can you try catch Throwable, just in case a java.lang.Error was thrown instead. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Any-idea-why-this-simple-splitter-is-not-working-in-2-10-SNAPSHOT-tp5678336p5683052.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/
