- Have a single and complete source fo events, as today we can listen
for events using different concepts:
Some of them seems overlapping a little so we may create 'contextual'
listeners like RouteEventListener, ExchangeEventListener, etc and
then i.e. the RoutePolicy could extend only what make sense for the
context so for the camel context prospective only an event has to be
fired. Listeenrs can eventually throw an uncheckd "VetoedException"
if the operation should not be done (i.e. a policy may prevent to
stop or start a route if certain circumstances).