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

Excellent! Congratulations. On Tue, Sep 27, 2016 at 1:18 AM, ncsibra wrote: > 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

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

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

Were you able to finally get it to work correctly? On Mon, Sep 26, 2016 at 1:10 AM, ncsibra wrote: > 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

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

I don't using weaving in my tests so can't be of a whole lot of help. Personally I'd try separating the single weave and double into two separate test files and see if there's any difference. It isn't too surprising that it fails with multiples especially with exception handling given the

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

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: