I'm too new to the Camel and ESB world to give a definitive answer to this,
but I think those route managing capabilities are useful if Camel is running
as a standalone application.
In my case, I don't need the integration and JBI capabilities of ServiceMix
but only an easy way to define
- can I get a single RouteDefinition, or only a list that I must iterate
to
find the one I am looking for?
The API is what we got. But we are open for API changes in Camel 2.0
so if you have suggestions what
you would like changed/added that feedback is much appreciated.
I think a pre
Thanks, that's exactly what I was looking for. But after looking at the
JavaDocs and writing a simple test application, there are still some points
I do not understand, maybe you can help me to clarify them:
- is there a way to avoid duplicated routes? (I tried to set an unique ID,
but I could
There are some older post on this topic in the forum, but I could not figure
out if the answers are still up to date. So is it possible to remove routes
from the CamelContext to add updated ones at runtime? And what happens with
messages on a route that are not delivered when the route stops or
2009/3/6 m.s. da_...@arcor.de:
There are some older post on this topic in the forum, but I could not figure
out if the answers are still up to date. So is it possible to remove routes
from the CamelContext to add updated ones at runtime? And what happens with
messages on a route that are not
