Re: weaveAddFirst doesn't work correctly with route level onException

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

Re: weaveAddFirst doesn't work correctly with route level onException

Thanks Ranx, the documentation actually says, that "It is recommended to only advice a given route once". I use advice on 2 separate route, those just built by 1 route builder, so based on the documentation, shouldn't have any kind of error. -- View this message in context:

Re: weaveAddFirst doesn't work correctly with route level onException

Upload a corrected file, which starts the route after adviceWith setup, but doesn't matter, it fails with the same exception. OnExceptionTest.java -- View this message in context:

weaveAddFirst doesn't work correctly with route level onException

Hi, I'm using camel version 2.17.1 and I have some problem with the weaveAddFirst method. When a route level onException clause exist and only one advice added or multiple advice added, but the first one contains the weaveAddFirst method, then camel will throw an exception:

Re: weaveAddFirst doesn't work correctly with route level onException

Can somebody confirm that am I doing something wrong or is this really a bug? -- View this message in context: http://camel.465427.n5.nabble.com/weaveAddFirst-doesn-t-work-correctly-with-route-level-onException-tp5787900p5787949.html Sent from the Camel - Users mailing list archive at

Re: weaveAddFirst doesn't work correctly with route level onException

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