You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2013/10/22 09:31:43 UTC

[jira] [Resolved] (CAMEL-5399) New component camel-dynamicep

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

Christian Schneider resolved CAMEL-5399.
----------------------------------------

    Resolution: Won't Fix

After looking into this again I think it is not worth to complicate endpoint syntax for this use case. It should be possible to adapt toolings to the syntax we already offer.

> New component camel-dynamicep
> -----------------------------
>
>                 Key: CAMEL-5399
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5399
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 3.0.0
>
>         Attachments: camel-dynamicep.zip, RouteDefinitionHelper.java.patch
>
>
> I have written a new camel-component that allows to listen on a dynamic list of endpoints. It works like this
> from("dynamicep:file:test,jms:myqueue")...
> So you simply supply a list of normal endpoints separated by commas. 
> Some things we need to decide are:
> - Name of the component. I am not sure if dynamicep i ideal. Any better names?
> - Syntax of the endpoint URI. I am not sure if the combinded URI is a valid URI
> I currently set the Fix version to 3.0.0 but we can easily backport this.



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