You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/02/18 08:28:11 UTC

[jira] [Commented] (CAMEL-8369) weaveAddLast does not work property when route ends with a split

    [ https://issues.apache.org/jira/browse/CAMEL-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325530#comment-14325530 ] 

Claus Ibsen commented on CAMEL-8369:
------------------------------------

Yeah last has to be last of the siblings - and not last of the children.

If you do this as a workaround then it works
weaveByType(SplitDefinition.class).after().log("weaveAddLast: ${body}").to("mock:result");

> weaveAddLast does not work property when route ends with a split
> ----------------------------------------------------------------
>
>                 Key: CAMEL-8369
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8369
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.14.1
>            Reporter: Chris Pimlott
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.14.2, 2.15.0
>
>         Attachments: WeaveAfterLastSplitTest.java
>
>
> When using AdviceWithRouteBuilder to modify a route definition, weaveAddLast does not work correctly when the route ends with a split.  It appears to add the additional components within the split, not afterwards.
> See attached testcase.
> Adding a trivial operation after the split in the original route builder fixes it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)