Hello Camel Developers! I have rather fundamental question already stated in the topic of this email. In typical scenario the answer is obvious but what about traversing exception causes?
.doTry() .throw(new RuntimeCamelException(new CamelException())) .doCatch(CamelException) // What is here in EXCEPTION_CAUGHT header? .end() currently it works this way (pseudocode, but everyone should catch it I guess) that doCatch is invoked, because it traverses exception causes to find a match. But even if it matches CamelException it will put RuntimeCamelException into EXCEPTION_CAUGHT header. I believe that it should be rather what we actually wanted to caught. Maybe both things in different headers. But I guess people assume that they catch what they are catching. I have a fix for it already, but wanted to know your opinions on it. Roman
