[
https://issues.apache.org/jira/browse/CAMEL-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan resolved CAMEL-5566.
-----------------------------------
Resolution: Fixed
see rev 1380791 and the examples/camel-example-cdi in the MyRoutes class
http://svn.apache.org/viewvc/camel/trunk/examples/camel-example-cdi/src/main/java/org/apache/camel/example/cdi/MyRoutes.java?revision=1380791&view=markup
> 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
>
>
> 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
