You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2008/02/11 18:50:36 UTC

[jira] Updated: (CAMEL-280) Dynamic Router implementation

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

Hadrian Zbarcea updated CAMEL-280:
----------------------------------

    Affects Version/s:     (was: 1.3.0)
                       1.4.0

> Dynamic Router implementation
> -----------------------------
>
>                 Key: CAMEL-280
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-280
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Przemyslaw Budzik
>            Priority: Minor
>             Fix For: 1.3.0
>
>         Attachments: dynamic-router.patch
>
>
> I decided to get my hands dirty by taking https://issues.apache.org/activemq/browse/CAMEL-8 :) I had in mind a feature like this:
> from("....").dynamicRouter(myRouter);
> where myRouter is a class that implements some interface so that it provides a list of endpoints (or one endpoint as well) to send messages to. Of course it creates some room for further improvements like providing Drools integration or another sophisticated routing mechanism based on "rules" so to speak. The idea is to have message and depending on its content create destinations dynamically per flow. 
> Anyway when expressed by DSL it's quite nice to use (however still the same is doable playing with processors). What do you think about it? Does it make sense?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.