Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-11566

Unified events in CamelContext

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 3.x
    • Component/s: camel-core
    • Labels:
      None
    • Estimated Complexity:
      Advanced

      Description

      • 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).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                lb Luca Burgazzoli
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: