camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CAMEL-4564) Make dynamicRouter conformant to the pattern
Date Tue, 22 Oct 2013 08:35:44 GMT

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

Christian Schneider edited comment on CAMEL-4564 at 10/22/13 8:34 AM:
----------------------------------------------------------------------

That is a good idea. Unfortunately recipientlist only works for one way calls. As far as I
recall it does not return the result. This is understandable as it has to cope with many endpoints
and returning a result only makes sense if you have one endpoint. 

So I agree that recipientlist is a good choice if it can return a result.

What do you think? Should we change recipientlist to return a result if there is only one
recipient or rather have a separate dsl element for that case?


was (Author: chris@die-schneider.net):
That is a good idea. Unfortunately recipientlist only works for one way calls. As far as I
recall it does not return the result. This is understandable as it has to cope with many endpoints
and returning a result only makes sense if you have one endpoint. 

So I agree thaat recipientlist is a good choice if it can return a result.

What do you think? Should we change recipientlist to return a result if there is only one
recipient or rather have a separate dsl element for that case?

> Make dynamicRouter conformant to the pattern
> --------------------------------------------
>
>                 Key: CAMEL-4564
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4564
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 2.8.1
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: Future
>
>
> Currently the dynamic router loops over evaluating the expression and sending to the
endpoint till the expression returns null.
> This is not really what the EIP dynamic router says. The pattern says "the Dynamic Router
evaluates all rules and routes the message to the recipient whose rules are fulfilled".
> So for me this sounds like we should only send to one endpoint.
> So my proposal is to change the dynamicRouter so it simply evaluates the expression as
a uri and routes to this destination if it is not null else it simply passes the exchange
to the next processor.
> As some people may use the loop functionality I propose to add a new DSL element that
mimics the current behaviour. A first proposal for a name is .loopTo(Expression) . So this
means loop and send to the endpoint specified by the expression. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message