[
https://issues.apache.org/jira/browse/CAMEL-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598317#comment-13598317
]
Antonin Stefanutti commented on CAMEL-5566:
-------------------------------------------
Hello Łukasz, I agree that enabling multiple Camel contexts in the CDI
container raises further questions regarding the way {{CdiRegistry}} are
managed as well as the scope of visible beans. I know that
[~romain.manni-bucau] came up with a {{@ExchangeScoped}} scope in
[camel-cdi-extension|https://github.com/rmannibucau/camel-cdi-extension]. Maybe
a {{@ContextScope}} would be needed.
I understand that the topic is more complex than it seems. As my knowledge
about CDI and Camel is still fairly limited, though my need to have multiple
Camel contexts remains, I'd be happy to contribute given your guidance. Maybe
we can create a dedicated issue to follow this up if you're still considering
the need as valid.
> 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
