camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: isMockEndpointsAndSkip documentation unclear
Date Mon, 16 Feb 2015 12:13:22 GMT

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.

On Mon, Feb 16, 2015 at 1:03 PM, Chris Melikian <> wrote:
> In, 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
> isMockEndPointsAndSkip() example only mocks one so is not equivalent.
> The "Mocking existing endpoints using the camel-test component" section
> shows an example for isMockEndpoints() where a wildcard is used but there is
> nothing to say that isMockEndpointsAndSkip doesn't allow wildcards. This is
> in line with my experience where I can return "direct:success" from
> isMockEndpointsAndSkip() and my expectation passes but when I use "*" or
> "direct:*" or "direct:.*" my expectation fails.
> It would be good to clarify whether the isMockEndpointsAndSkip() method can
> support multiple endpoints or single and include an example of multiple
> endpoints if this is indeed possible. I'm using Camel 2.14.1.
> Best regards, Chris.
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Red Hat, Inc.
Twitter: davsclaus
Author of Camel in Action:

View raw message