You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/02/08 11:27:00 UTC

[jira] [Assigned] (CAMEL-14525) provide a bean definition to the auto configuration by property feature

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

Claus Ibsen reassigned CAMEL-14525:
-----------------------------------

    Assignee: Claus Ibsen

> provide a bean definition to the auto configuration by property feature 
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-14525
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14525
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-main
>            Reporter: Andrea Tarocchi
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.1.0
>
>
> As discussed with [~davsclaus], would be very nice to have a mechanism in property auto configurations to define beans in their own namespace i.e. in order to make something like this possible:
> {code:sh}
> camel.bean.mycf=#class:my.package.MyCf
> camel.bean.mycf.brokerUrl=localhost:61616
> camel.bean.mycf.username=admin
> camel.bean.mycf.password=admin
> camel.component.sjms2.connectionFactory=#mycf
> {code}
> by instantiating, initializing and adding to the registry the {{mycf}} bean;
> that would nicely enhance the current autoconfiguration mechanism and actually play quite nicely with the registry auto-discovery of single implementation factories (i.e. making the {{camel.component.sjms2.connectionFactory=#mycf}} unnecessary)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)