[CAMEL-11565] Modular DefaultCamelContext in terms of loading and starting routes

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.10.0
• Component/s: camel-core
• Estimated Complexity: Advanced
• Assignee: Unassigned
• Reporter: Luca Burgazzoli
• Created: 20/Jul/17 05:19
• Updated: 27/Apr/21 12:30
• Resolved: 27/Apr/21 12:30

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

Issue Links

• is related to: CAMEL-11443 Add a RouteController SPI to allow to customize routes life-cycle
• is related to: CAMEL-14053 Routes Loader SPI
• links to: List discussion