[jira] [Updated] (CAMEL-11565) Modular DefaultCamelContext in terms of loading and starting routes

["Claus Ibsen (JIRA)" <ji...@apache.org>]

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

Claus Ibsen updated CAMEL-11565:
--------------------------------
    Summary: Modular DefaultCamelContext in terms of loading and starting routes  (was: Modular DefaultCamelContext)

> Modular DefaultCamelContext in terms of loading and starting routes
> -------------------------------------------------------------------
>
>                 Key: CAMEL-11565
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11565
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Luca Burgazzoli
>            Priority: Major
>             Fix For: 3.x
>
>
> - 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



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)