Thanks for the tip, RoutePolicy or controlling the route from the
CamelContext could do the trick.
The problem that we need to solve is still in a feasibility stage but since
we have the ability to define the interface I am inclined to suggest that
the message producer will include all pending mess
Did you already had a look at [1]?
IMO this is the way you should go. I'm working on an example for my
colleges, which have similar needs:
- The route should started/triggered by an external scheduler (Tivoli in
our case). We will use camel-netty, camel-mina or camel-http4 for this.
- The route sh
