> 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
ssage in context:
http://camel.465427.n5.nabble.com/Help-with-mocking-a-filter-bean-method-call-tp5727543p5727665.html
Sent from the Camel - Users mailing list archive at Nabble.com.
> 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 again!
--
View this message in context:
http://camel.465427.n5.nabble.com/Help-with-mocking-a-filter-bean-method-call-tp5727543p5727552.html
Sent from the Camel - Users mailing list archive at Nabble.com.
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
this message in context:
http://camel.465427.n5.nabble.com/Help-with-mocking-a-filter-bean-method-call-tp5727543.html
Sent from the Camel - Users mailing list archive at Nabble.com.
