> I will be going the route of using the spring based registry. Looks like
> exactly what I need and have had good luck with it so far.
Great to hear that. Feel free to drop us a line if you need any further advice.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Thanks for the response. I agree I shouldn't put mocks into our int tests,
but the lovely code with this in it, I inherited.
I will be going the route of using the spring based registry. Looks like
exactly what I need and have had good luck with it so far.
Thanks again!
--
View this message in
> In my actual test, my bean is loaded up with spring
> component scan (most of the tests that use this are integration tests)
Actually I would not advice putting Mockito mocks into integration
tests, as the latter approach makes your test hard to maintain and
control.
But of course you can confi
Thanks for the quick reply!
This will work for this example, but I only created this example for
simplicity sake. In my actual test, my bean is loaded up with spring
component scan (most of the tests that use this are integration tests) and
the test is initialized with overriding the createApplica
Hi Spencer,
Welcome to our community :) .
> from('direct:start').filter().method('bean',
> 'matches').to('mock:endpoint').stop()
>
> In my test, I am trying to mock out the method 'matches' call using mockito.
The approach of mine choice would be to register Mockito mock in the
Camel registry un
