[
https://issues.apache.org/jira/browse/CAMEL-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594711#comment-13594711
]
Antonin Stefanutti commented on CAMEL-5566:
-------------------------------------------
Hello Łukasz, in my case, I have a CDI container starting with multiple bean
archives in the classpath, each containing multiple beans annotated with
{{@ContextName}}. Ideally, I'd like to have each bean archive and the routes
within it executing in a dedicated Camel context.
Obviously, this can work with a single Camel context. Though for the sake of
monitoring, operability and understanding of the system, I'd rather prefer
structuring the runtime execution in multiple Camel contexts. Besides, from my
understanding of the Camel CDI codeline, it seems closer in terms of code
changes to having the multiple Camel contexts support enabled rather than
removing all the related code.
> provide an annotation to auto-register a RouteBuilder with a CamelContext
> (lazily creating a new CamelContext if a different contextName is specified)
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-5566
> URL: https://issues.apache.org/jira/browse/CAMEL-5566
> Project: Camel
> Issue Type: Improvement
> Components: camel-cdi
> Reporter: james strachan
> Assignee: james strachan
> Fix For: 2.11.0
>
> Attachments: CAMEL-5566.patch
>
>
> 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).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
