Description
as per Romain's ideas on the dev list, it would be nice to have an annotation to make it easy to inject a RouteBuilder instance then bind it to a CamelContext (basically creating the CamelContext for the given context name and calling CamelContext.addRoutes(routes)).
Previously Romain had gone with @CamelContextId though am thinking, @Named is the way of associating an id/name with a bean and its really more about camel lifecycles, so thinking of using @CamelStartup to make it more obvious what it does (with the contextName being an optional parameter too; since multiple contexts within the same class loader are kinda rare - there's no huge need for more than one CamelContext).
Attachments
Attachments
Issue Links
- is related to
-
CAMEL-5422 Align camel cdi integration with other dependency injection containers
- Resolved