You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/10/09 12:39:00 UTC
[jira] [Updated] (CAMEL-11565) Modular DefaultCamelContext in terms
of loading and starting routes
[ https://issues.apache.org/jira/browse/CAMEL-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-11565:
--------------------------------
Fix Version/s: (was: 3.6.0)
3.7.0
> 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.7.0
>
>
> - 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
(v8.3.4#803005)