You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/08/30 08:30:38 UTC

[jira] [Updated] (CAMEL-4391) Support for marking a CamelProxy as a primary or non-primary spring bean

     [ https://issues.apache.org/jira/browse/CAMEL-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-4391:
-------------------------------

         Priority: Minor  (was: Major)
    Fix Version/s: Future
       Issue Type: New Feature  (was: Improvement)

> 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
>
>
> 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