camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Camel 2.0+ functionality - dynamic route and endpoint creation?
Date Fri, 05 Jun 2009 07:38:59 GMT

Did my mail ever get to the user forum? I had some mail issues with my
mails being denied that day.
See below for answers.

---------- Forwarded message ----------
From: Claus Ibsen <>
Date: Wed, Jun 3, 2009 at 10:31 AM
Subject: Re: Camel 2.0+ functionality - dynamic route and endpoint creation?


On Tue, Jun 2, 2009 at 11:47 PM, michael.olson <> wrote:
> 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.

In Camel 2.0 James added the camel web-console that is a web based
console for dynamic routing and viewing routes and the likes.

There should be a link to it on the camel wiki pages. Just use the
google custom search bar.

And James recently replied to the Google Summer of code Project to
improve the web console

Yes you can at runtime add routes etc.
There are methods on CamelContext to do that.

You can build the routes using the model classes. That is what the DSL does.

And there should be a few unit tests in camel-core about mutating the
route at runtime.
For instance: StartAndStopRoutesTest

> 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:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Apache Camel Committer

Open Source Integration:

Claus Ibsen
Apache Camel Committer

Open Source Integration:

View raw message