I don't want to be nagging, but personally I wouldn't go down the route
(hmm...nice play of words) of
creating routes dynamically from the application. Personally I would
stick to having the route in my
source code and therefore tagged and released and tested etc.
Generating the config can only break so much ...
In other words, leave the structure untouched, but keep the endpoints
flexible. For example, what if
you wanted to add a wiretap later on for some kind of auditing ?
In one of my applications I use a similar pattern and have the endpoints
flexible and reconfigurable via JMS
control messages.
My 2ct
Andreas
On 09/06/2013 09:48 AM, Gnanaguru S wrote:
Thanks for the clarification Charles & Andreas, I understand. I hope there
is a roadmap for this in Camel 3.0 .
Claus, This is the best available solution as of now, which I consider using
it.
Cheers,
Guru
gnanaguru.com
--
View this message in context:
http://camel.465427.n5.nabble.com/Web-based-camel-route-automation-tp5738797p5738829.html
Sent from the Camel - Users mailing list archive at Nabble.com.
