Yes, changed the method call order. :D We are doing several weave* calls, just put a weaveById first, then it works fine. Actually, in our case, we have to put it last to be sure that our advice is the last(actually the first :)), so it's not just a hack. Anyway, I may report a bug on their issue tracker as far as I see, they don't really check this thread.
-- View this message in context: http://camel.465427.n5.nabble.com/weaveAddFirst-doesn-t-work-correctly-with-route-level-onException-tp5787900p5788085.html Sent from the Camel - Users mailing list archive at Nabble.com.
