[ https://issues.apache.org/jira/browse/CAMEL-11196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981223#comment-15981223 ]
Claus Ibsen commented on CAMEL-11196: ------------------------------------- We should also make it easy to reuse an existing connector and have separate configuration, eg so the same user can use a twitter-connector and then configure it for user A and user B in the same application without configuration clashes. Today the component level would reuse the same component / configuration. So we may want to find a way to clone a component or whatever we can think of. A little bit of problem is the generated spring boot auto configuration which is hard-coded to one prefix. > Camel connectors - Allow to configure in one place and let it figure out > component vs endpoint level > ---------------------------------------------------------------------------------------------------- > > Key: CAMEL-11196 > URL: https://issues.apache.org/jira/browse/CAMEL-11196 > Project: Camel > Issue Type: Improvement > Components: camel-connector > Reporter: Claus Ibsen > Fix For: 2.20.0 > > > A Camel connector can be configured on two levels > - component > - endpoint > Just like a regular Camel component. > But we should allow users to configure a connector in one place, and not > worry about if its component or endpoint level. And then let camel-connector > when it prepares the connector figure out all of this for you. > This may require supporting loading configuration from external resource > files such as .properties files etc. Or something else. But from end users we > can make this easier. -- This message was sent by Atlassian JIRA (v6.3.15#6346)