camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tarun Kumar <agrawal.taru...@gmail.com>
Subject Re: Is onFinally() compulsory after doCatch()?
Date Tue, 02 Jul 2013 08:36:14 GMT
Above link doesn't answer my second ques. Could you please help?


On Tue, Jul 2, 2013 at 12:41 PM, Christian Müller <
christian.mueller@gmail.com> wrote:

> Check out the link I already sent to you [1].
>
> [1] http://camel.apache.org/try-catch-finally.html
>
> Best,
> Christian
> -----------------
>
> Software Integration Specialist
>
> Apache Camel committer: https://camel.apache.org/team
> V.P. Apache Camel: https://www.apache.org/foundation/
> Apache Member: https://www.apache.org/foundation/members.html
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
>
>
> On Tue, Jul 2, 2013 at 7:50 AM, Tarun Kumar <agrawal.tarun23@gmail.com
> >wrote:
>
> > my route looks like this:
> >
> > from().
> > .toTry().process()
> > .doCatch(Exception.class)
> > .to().to().process()
> > .end()
> >
> >
> > My questions are:
> >
> > 1. is .doFinally compulsory after doCatch()?
> > 2. In my case, how does route know whether second .to() in line 4 is
> inside
> > doCatch() or after doCatch()?
> > 3. I am using cxfrs component, why is my exchange body not being returned
> > back to caller. Caller is seeing 204 no content found. While, when i
> remove
> > doTry and doCatch() with same code, caller is able to see proper response
> > (exchange body, status and all). Why is that?
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message