Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Won't Fix
-
None
-
None
-
Unknown
Description
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.
Attachments
Issue Links
- relates to
-
CAMEL-15560 generic route loader
- Resolved