I'm very interested in the Camel architecture and in what it supports. My only problem thus far has been in the static nature of the definitions of the routes and components. I am curious as to what extent Camel can handle dynamic configuration. I have spent quite a bit of time reviewing the documentation for both the current version of Camel and the milestone release for Camel 2.0, and I have been unable to find exactly what I'm looking for. I'm hoping that someone in the community can either steer me to the appropriate information, or let me know that the architecture simply can't handle what I want.
Here is the scenario. I'd like to be able to start up a more or less 'blank' Camel instance, with only one running bean and no existing routes. I would like to put that bean in charge of creating other beans/endpoints and making and changing routes between them. So, the questions are: - Can I programatically create and delete beans/endpoints and create/mutate/delete routes with no prior configuration? i.e. there is zero hardcoding of the definitions of the beans/endpoints/routes; that will all be supplied to the sole running bean as a parameter. If not, can anyone speculate as to the amount of work that would be required to adapt the architecture to support this? I'd be interested in contributing this type of functionality to the project if it seems that it would fit with the existing infrastructure, but if not I'll have to look for another mechanism to implement this. If it helps, I can elaborate further on what I'd like to implement. Thanks in advance, - Michael -- View this message in context: http://www.nabble.com/Camel-2.0%2B-functionality---dynamic-route-and-endpoint-creation--tp23841602p23841602.html Sent from the Camel - Users mailing list archive at Nabble.com.
