Claus,
It's rather a matter of business logic to get routes stopped in particular
order.
Jakub,
> The framework itself has no insight into the possible values that
> the POJO could return, and therefore cannot make any judgements as to
> the startup ordering of the routes.
And the way to fix
Greetings!
Currently Apache Camel can have route dependencies hardcoded through
numbers, which doesn't really work well, when multiple route builders are
involved and they have overlapping order numbers. -
http://camel.apache.org/configuring-route-startup-ordering-and-autostartup.html
Given follo
Greetings,
Currently i have an aggregation route with approximately following
configuration:
.aggregate(header("kind"))
.aggregationRepository(getHdfsFlushRepo())
.optimisticLockRetryPolicy(new
OptimisticLockRetryPolicy().maximumRetries(10).randomBac
