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/07/12 00:21:04 UTC

[jira] [Resolved] (CAMEL-3671) AggregationStrategy - Allow to access original Exchange in the parameter list

     [ https://issues.apache.org/jira/browse/CAMEL-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-3671.
--------------------------------
    Resolution: Won't Fix

Will just be too complicated

> AggregationStrategy - Allow to access original Exchange in the parameter list
> -----------------------------------------------------------------------------
>
>                 Key: CAMEL-3671
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3671
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 3.0.0
>
>
> Where we use {{AggregationStrategy}} we should allow a more bean like approach where bean parameter binding is being used.
> Also we should allow end user to bind a parameter with the original exchange so they can grab information from it.
> We need some sort of @Qualifier to define the scope.
> {code}
> public void myAggregate(@Header(value = "username", qualifier = Original) String username, @Body(qualifier = Old) String oldBody, @Body(quailifer = New) String newBody);  
>   ...
> {code}
> The API is not set. Also the qualifier could be named scope or something. And the last two parameters could have convention over configuration, 1st = old, 2nd = new.



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