Hi,
try to simplify your route by using direct endpoints.
The ChoiceProcessor tends to behave strangely when the route gets more
complex.
.from()
...
.doTry()
...
.log(level.INFO, log, "Reaches point 1.")
.endDoTry()
.doCatch(MyHttpException.class)
I ran into this today. I have a route with doTry/doCatch, where in the
doCatch there is a choice()when()otherwise() block. The code never reaches
"point 2" for me, even when MyHttpException is not thrown.
.from()
...
.doTry()
...
.log(level.INFO, log, "Reaches point
Hi Claus,
Thanks for you response.
I can only see endDoTry(), not endDoCatch().
Should I use endDoTry() to end the inner doTry-doCatch block?
I am using Camel 2.11.0.
Thank you.
Jose
--
View this message in context:
http://camel.465427.n5.nabble.com/Nested-doTry-doCatch-blocks-tp574856
Hi
Yeah you can do that though its not as often seen in use.
See this FAQ
https://camel.apache.org/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.html
When using java dsl you may need to use endXXX to make the compiler happy.
On Mon, Mar 10, 2014 at 4:46 PM, Jose wrote:
> Is it poss
