[
https://issues.apache.org/jira/browse/CAMEL-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-11566.
---------------------------------
Resolution: Won't Fix
> Unified events in CamelContext
> ------------------------------
>
> Key: CAMEL-11566
> URL: https://issues.apache.org/jira/browse/CAMEL-11566
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Luca Burgazzoli
> Priority: Major
>
> - Have a single and complete source fo events, as today we can listen
> for events using different concepts:
> - LifecycleStrategy
> - StartupListener
> - EventNotifier
> - RoutePolicy
> 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).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
