camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5399) New component camel-dynamicep
Date Wed, 27 Jun 2012 09:49:44 GMT


Christian Schneider commented on CAMEL-5399:

Not exactly. There are some substantial differences that made me code this.

In the dynamicep component the exact same route is used while in your example there are two
Using direct endpoints this could be achieved like:

As you can use property placeholders in the uri you can have a dynamical list of endpoints
to listen on:
So this allows to listen on a list of endpoints where the number of endpoints to listen on
is not known at compile time. We use this for a customer that wants to listen on a larger
list of jms queues.
This behaviour is quite difficult to mimic without the new component.

> New component camel-dynamicep
> -----------------------------
>                 Key: CAMEL-5399
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message