At the bottom it talks about intercept() but doesn't use it. Confusing at
least!
And the link to InterceptorProcessor is a 404.
James
I encountered this problem as well when I first used this.
Because you used the star, it mocked and skipped every endpoint, including the
start of your route. Just ensure the regex you provide doesn't match the start
of your route. If you enable camel logging at info level, you'll see
Thanks Claus, so how come:-
@Override
public String isMockEndpointsAndSkip() {
return *;
}
gives me a failure but
@Override
public String isMockEndpointsAndSkip() {
return direct:success;
}
works in my test?
I'm
Hi,
about the mocked service registry, I don't think so. It required some
specialty that is actually only available with a OSGi framework bundle.
Therefore I doubt it.
regards, Achim
2015-02-16 11:38 GMT+01:00 Arnaud Deprez arnaudep...@gmail.com:
Thx for your answer, I'll read your blog :-).
Thx for your answer, I'll read your blog :-).
Is it possible to imagine to have such an improvement in the mocked service
registry ?
I think it would be nice if we can unit test our jpa stuff (like with
spring) without having to run a complete karaf container for each test.
Arnaud
2015-02-15
In http://camel.apache.org/mock.html, under the heading Mocking endpoints
and skip sending to original endpoint, there are two examples, one using
adviceWith() and the other using isMockEndpointsAndSkip() for mocking
existing endpoints. The adviceWith() example mocks two endpoints whereas the
Hi
Yeah it uses the same endpoint pattern matching as the interceptor
does, so you can use jms* (using wildcard) for all jms endpoints eg.
Or use a regular expression for more advanced.
http://camel.apache.org/intercept
On Mon, Feb 16, 2015 at 1:03 PM, Chris Melikian ch...@melikian.net wrote:
