Re: Spring boot + MockEndpointsAndSkip + DirtiesContext

Thanks for quick reply. Turned out I was using the wrong runner class in the @RunWith annotation. Following Claus instructions in the ticket solved the issue. Thanks Pontus On Tue, 10 Jan 2017 at 23:24 Minh Tran wrote: > Hi Pontus, > > Yep I ended up raising this > https://issues.apache.org/ji

Re: Spring boot + MockEndpointsAndSkip + DirtiesContext

Hi Pontus, Yep I ended up raising this https://issues.apache.org/jira/browse/CAMEL-9332 It was fixed when I last checked this in 2.17.1. Not sure about 2.18.0 though. > On 11 Jan 2017, at 9:13 am, Pontus Ullgren wrote: > > Hi, > > Did anyone

Re: Spring boot + MockEndpointsAndSkip + DirtiesContext

Hi, Did anyone ever raise a Jira for this issue ? It seems that @MockEndpointAndSkip still (2.18.0) does not work. Best regards Pontus Ullgren On Tue, 9 Aug 2016 at 02:59 Minh Tran wrote: > Hi, should I raise a jira for this? > > > On 5 Aug 2016, at 10:03 AM, Minh Tran wrote: > > > > Hi > >

Re: Spring boot + MockEndpointsAndSkip + DirtiesContext

Hi, should I raise a jira for this? > On 5 Aug 2016, at 10:03 AM, Minh Tran wrote: > > Hi > > I am using Camel 2.17.2, Spring Boot 1.3.6 and seeing strange behaviour in my > unit tests. I’ve simplified it to the following example > > @RunWith(CamelSpringBootJUnit4ClassRunner.class) > @SpringA

Spring boot + MockEndpointsAndSkip + DirtiesContext

Hi I am using Camel 2.17.2, Spring Boot 1.3.6 and seeing strange behaviour in my unit tests. I’ve simplified it to the following example @RunWith(CamelSpringBootJUnit4ClassRunner.class) @SpringApplicationConfiguration @MockEndpointsAndSkip("direct:b") @DirtiesContext(classMode = ClassMode.AFTER_