camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Mocking an endpoint within a try-catch block
Date Thu, 07 Feb 2013 14:26:17 GMT
On Thu, Feb 7, 2013 at 3:08 PM, fordm <ford.j.martin@gmail.com> wrote:
> Claus Ibsen-2 wrote
>> Have you tried with
>>
>>          weaveById(endpointId).replace().to(newUri);
>
> Removing the selectFirst I get the same result.
>
> However, if I use
>
>     weaveByToString(uriPattern).selectFirst().replace().to(newUri);
>
> then the end point seems to be mocked successfully. Which is fine for the
> particular test I'm writing, but it would be good to know why I'm not able
> to mock endpoints by id.
>

Yeah the idea is that it does not matter how you match the nodes to mock.
Fell free to log a JIRA ticket, as this smells like a bug
http://camel.apache.org/support


>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Mocking-an-endpoint-within-a-try-catch-block-tp5727081p5727127.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Mime
View raw message