Reading your requirements it seems to me you need a really "dynamic" &
"flexible" routing-configuration at runtime, so that IMHO I would say Apache
Camel JMX-support would provide you a better solution (instead of xml-based
configuration).
Just as an idea, but maybe the camel riders have better solution in mind:
As the existence of at least *one* route in each given camel context is
mandatory you could *statically* setup all of those hundreds of Camel
contexts of yours to have a dummy route like:
from("direct:start").to("direct:end");
which would be the first step of your deployment, the second step then would
be to *feed* all those routes of yours through JMX. Ben [1] is also one of
the riders who could give you some inspiration of the idea I justed talked
about. Of course in your case that JMX-Route-Feeder-Tool could be as simple
as a java command-line-tool but also as nice as [2].
[1]
http://www.consulting-notes.com/2010/08/managing-camel-routes-with-jmx-apis.html
[2] http://camel.apache.org/web-console.html
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Loading-two-camel-context-files-at-start-tp5049449p5054803.html
Sent from the Camel - Users mailing list archive at Nabble.com.
