[jira] [Reopened] (CAMEL-12529) Dynamic Router implementation behavior inconsistent with Dynamic Router EIP specification

["Steve Storck (JIRA)" <ji...@apache.org>]

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

Steve Storck reopened CAMEL-12529:
----------------------------------

Reopening pending further discussion.

> Dynamic Router implementation behavior inconsistent with Dynamic Router EIP specification
> -----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-12529
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12529
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.19.2
>            Reporter: Steve Storck
>            Priority: Major
>
> Currently, the Dynamic Router component of camel-core repeatedly routes messages back through the dynamic router, as indicated in the documentation. However, when examining the Dynamic Router EIP specification at [http://www.enterpriseintegrationpatterns.com/patterns/messaging/DynamicRouter.html], we can see that this behavior is not consistent with the specification.
> The description is:
> {quote}Use a Dynamic Router, a Router that can self-configure based on special configuration messages from participating destinations.
> Besides the usual input and output channels the Dynamic Router uses an additional control channel. During system start-up, each potential recipient sends a special message to the Dynamic Router on this control channel, announcing its presence and listing the conditions under which it can handle a message. The Dynamic Router stores the 'preferences' for each participant in a rule base. When a message arrives, the Dynamic Router evaluates all rules and routes the message to the recipient whose rules are fulfilled. This allows for efficient, predictive routing without the maintenance dependency of the Dynamic Router on each potential recipient.
> {quote}
> Since the documentation specifies the re-routing nature of the dynamic router quite clearly, this is obviously not an unintended side-effect or consequence but, I believe, a misunderstanding of the EIP itself.  It appears that there _might_ be a point of confusion with the control channel that connects the potential endpoints to the rule base. This is not for re-routing of the messages, but for the potential endpoints to register rules with the dynamic router. While I am not certain how this should (or would) be implemented within Camel, the current behavior is not quite consistent with the description of the EIP



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)