Yes, weaveById works fine, but in my case I use it in a base class, used by almost every integration test and those tests are able to modify the route too before start, so I can't be sure that my originally first node is really still the first after the child test set up phase, that's why I used and prefer the weaveAddFirst method. And every integration test using a different route with different ids, so a general solution with weaveAddFirst is better in my case.
-- View this message in context: http://camel.465427.n5.nabble.com/weaveAddFirst-doesn-t-work-correctly-with-route-level-onException-tp5787900p5788046.html Sent from the Camel - Users mailing list archive at Nabble.com.
