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

Claus Ibsen commented on CAMEL-5399:
------------------------------------

You can do today
{code}
from("file:test", "jms:myqueue").to("xxx")
{code}

Or stack multiple froms (maybe not so nice readable)
{code}
from("file:test").from("jms:myqueue").to("xxx")
{code}

The dynamiceip would IMHO only be interesting if it computes at route startup 
time (eg runtime) the incoming endpoints to the route.
{code}
from("dynamiceip:bean:myInputs").to("xxx")
{code}

And then myInputs could be a expression that returns a 1..n uris of endpoints, 
or Endpoint instances. And with the simple expression we could read the uris 
from a .properties file etc.
{code}
from("dynamiceip:simple:${properties.myInputs}").to("xxx")
{code}

I guess the syntax needs to be worked a bit, but then you could dynamic decide 
the inputs to the route from various sources, easily pluggable using the Camel 
expression.

                
> 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
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to