You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Luca Burgazzoli (JIRA)" <ji...@apache.org> on 2017/07/20 05:30:00 UTC

[jira] [Updated] (CAMEL-11566) Unified events in CamelContext

     [ https://issues.apache.org/jira/browse/CAMEL-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luca Burgazzoli updated CAMEL-11566:
------------------------------------
    Estimated Complexity: Advanced  (was: Unknown)

> 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
>             Fix For: 3.0.0
>
>
> - 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
(v6.4.14#64029)