[ https://issues.apache.org/jira/browse/CAMEL-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David J. M. Karlsen updated CAMEL-4391: --------------------------------------- Attachment: test-context.xml TestCase.java SomeImpl.java SomeIface.java The attached testcase should show this pretty well > Support for marking a CamelProxy as a primary or non-primary spring bean > ------------------------------------------------------------------------ > > Key: CAMEL-4391 > URL: https://issues.apache.org/jira/browse/CAMEL-4391 > Project: Camel > Issue Type: New Feature > Components: camel-spring > Affects Versions: 2.8.0 > Environment: N/A > Reporter: David J. M. Karlsen > Priority: Minor > Labels: primary, proxy, spring > Fix For: Future > > Attachments: SomeIface.java, SomeImpl.java, TestCase.java, > test-context.xml > > > It would be very handy if a camelProxy bean (which is also a spring bean) > could be defined as primary (see > http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/htmlsingle/spring-framework-reference.html, > search for @Primary). > I have a content based route, which delegates to some other beans depending > on argument values to the proxy. All three beans implement the same > interface. So if I could just mark the proxy as primary that bean would be > preferred. > Other usecases where you would like it not to be primary probably exist as > well. > I suggest adding an optional boolean attribute "primary" which is by default > true. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira