camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Artur Jablonski <ajablon...@ravenpack.com>
Subject Re: Camel [2.19.3] + SpringBoot [1.5.6] fails executing two JUnit tests that succeed when run individually
Date Thu, 16 Nov 2017 14:49:23 GMT
Hey,

Nope, I tried with 2.19.4 and it was failing in the same way as 2.19.3. We
felt brave yesterday and moved to 2.20.1. What's the worst thing that can
happen? :)



On Thu, Nov 16, 2017 at 3:42 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:

> Hi
>
> If you want to stay on 2.19.x you may try 2.19.4 which could
> potentially also have the fix.
>
> On Wed, Nov 15, 2017 at 4:39 PM, Artur Jablonski
> <ajablonski@ravenpack.com> wrote:
> > Sweet lord! This must be the fastest response ever... and yes indeed it
> > works with 2.20.1.
> >
> > Thank you Claus
> >
> > Best,
> > Artur
> >
> >
> > On Wed, Nov 15, 2017 at 4:09 PM, Claus Ibsen <claus.ibsen@gmail.com>
> wrote:
> >
> >> Hi
> >>
> >> I think we fixed something related to that, try with camel 2.20.1.
> >> Or refactor your test classes to only have 1 test method when advicing
> >>
> >> On Wed, Nov 15, 2017 at 4:06 PM, Artur Jablonski
> >> <ajablonski@ravenpack.com> wrote:
> >> > Hello,
> >> >
> >> > I've been looking at this issue with running integration tests in
> Camel +
> >> > SpringBoot combo context.
> >> >
> >> > I have a route that fails to start in integration tests when
> CamelContext
> >> > starts up. That's expected. One of endpoints refers to a AWS resource
> >> that
> >> > the test running machine has no access to. That's OK too, I don't
> want to
> >> > poke the real resource in the test, so I use the adviceWith() to
> replace
> >> > the endpoint and start the camel context myself. This works well for a
> >> > single test. As soon as I add another test, the second test fails,
> >> because
> >> > of the complaints from the original endpoint about the permissions. It
> >> > looks as if before the second test runs the spring context starts up
> >> > together with the camel context (it seems to ignore the fact that the
> >> test
> >> > class is annotated with @UseAdviceWith).
> >> >
> >> > This is a minimal testcase I could produce to reproduce the behaviour
> >> > https://gist.github.com/anonymous/626cf26197dd5a05569d4d306870a22e
> >> >
> >> > What am I missing?
> >> >
> >> > Best,
> >> > Artur
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> http://davsclaus.com @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
> >>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message