[
https://issues.apache.org/jira/browse/CAMEL-14089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli resolved CAMEL-14089.
-------------------------------------
Resolution: Won't Fix
With the implementation of the generic route loader, include/exclude filter is
more than enough
> camel-main - Improve routes discovering
> ---------------------------------------
>
> Key: CAMEL-14089
> URL: https://issues.apache.org/jira/browse/CAMEL-14089
> Project: Camel
> Issue Type: Improvement
> Components: camel-main
> Reporter: Luca Burgazzoli
> Priority: Minor
> Fix For: 3.x
>
>
> Camel main has two main options to auto-discover routes:
> - by scanning the class path
> - by scanning the registry
> So it is possible that if a user adda a route to the registry
> programmatically, then the route is present twice and potentially leading to
> errors because it is also discovered from the classpath.
> There are some workaround for that, like:
> - configure routes inclusion/exclusion patterns
> - disable auto discovery
> But it would be nice if we can give to the use more control about the
> discovering process like to explicit mark routes from discovering with a
> dedicated annotation or reusing an existing one like @BindToRegistry.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
