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

Modular DefaultCamelContext in terms of loading and starting routes

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.10.0
    • camel-core
    • None
    • Advanced

    Description

      • Add a concept of RouteLoader which is in charge of building the route
        definitions from a source, to eventually monitor the source for
        changes and then refresh the contex so i.e. we can move the current
        process of loading routes from xml to a dedicated XMLRouteLoader. It
        should be possible to add more loaders so one can load routes from
        different sources (yaml, json, groovy)
      • Add a concept of RouteControler which is in charge of routes'
        life-cycle, this is partially done by CAMEL-11443 but for 2.x it will
        be more a placeholder that an concrete implementation as the
        life-cycle of routes involves quite a bit of code and it is quite hard
        to introduce a proper life-cycle manager without breaking the things.
        In my mind the camel context should be a bridge between RouteLoader
        and the RouteController then the specific route controller can do its
        job like:
      • start routes in parallel
      • handle reoutes dependencies (CAMEL-8599)
      • restart failing routes
      • etc

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            lb Luca Burgazzoli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment