Yes. Have a look at [1] and [2].
If you have a route like:
from("direct:start")
.enrich("jetty:xxx", aggregationStrategy)
.to("direct:yyy");
you can decide which payload is routed in your main route in your
aggregationStrategy. It can be the payload which arrived in the enricher,
the payload
To add to my previous post - basically I want to send a message out from
Jetty mid-route and then continue the route as is. Is this possible?
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-runTimeException-handling-tp5733659p5734059.html
Sent from the Camel - Us
Hi Claus,
So where is what I have accomplished:
1) I am in Bean 1.
2) I get the timer-expiry and handle it with OnException and I set it as
Continued because if I set it to handled, the pipe breaks and nothing goes
out to caller.
3) I set a reply message in exchange
4) NOW I need to wait for Bean
Hi
You can use onException to catch and handle the runtime exception, and
there you can do set some "reply message" you want to caller to see.
And remember to set a status code of 500+ if you want to tell the
caller that there was some internal server error etc.
And no you cannot route to bean2 a
Hi Claus,
Thanks for the quick reply but I think I explained my problem incorrectly.
So here I try again:
1) My route flows like HTTP Req -> Jetty -> Bean1 -> Bean 2 -> Route END.
After this a HTTP reply goes back to sender.
2) Now say for e.g. during bean 1 I encounter a timer expiry. I handle t
Hi
If you have a copy of Camel in Action, see chapter 5, section 5.4.5
You can tell Camel to continue with the onException.
You can find a bit of information on the Camel web site also about this.
On Mon, Jun 3, 2013 at 9:47 AM, suyash.singh wrote:
> Hi,
>
> We are developing an app using Ap
