On Wed, Jun 25, 2014 at 12:14 PM, Gnanaguru S <[email protected]> wrote:
> Hello
>
> Its my long pending doubt on using AOP stuffs in Camel while writing test
> cases.
>
> 1. weavebyid - works only with processors like Choice, doTry, Multicast. It
> doesn't work with endpoints. Especially with 'To' endpoints. ( For 'From'
> endpoint we anyway have ReplaceFromWith )
>
Should work with any ids assigned to nodes in the graph, eg
<to uri="someWhere" id="blah"/>
Then you can weaveById("blah")
> 2. weavebyToString - It works with 'To' endpoints. If we have a endpoint
> called <to ref="cloud-endpoint" />
> then why it expects a wild card like this ?
> weaveByToString(".*cloud-endpoint*.").remove();
ref is just a xml id, the endpoints do not know their xml id. An
endpoint has an uri which is all it knows.
>
> 3. If my 'To' endpoint is inside a processor like Choice . Then
> weaveByToString remove the choice also . Even if choice and the To endpoint
> have different id's.
>
Yeah that could be a bug, though the CBR is a special eip, so we may
need to add special log for it in the advice logic to handle it.
> Its manageable to write test cases with existing features, but Camel will
> become more interesting if these issues are sorted out :)
>
> A happy camel rider !
> Guru
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-AdviceWith-issues-tp5752786.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: [email protected]
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
