[jira] [Comment Edited] (CAMEL-10937) Camel components - Configured using setters should support property placeholders

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-10937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895649#comment-15895649 ] 

Claus Ibsen edited comment on CAMEL-10937 at 3/4/17 12:21 PM:
--------------------------------------------------------------

This is a standard option to turn on|off (on by default) on component and hence why every component now have generated that for spring boot etc


was (Author: davsclaus):
This is a standard option on component and hence why every component now have generated that for spring boot etc

> Camel components - Configured using setters should support property placeholders
> --------------------------------------------------------------------------------
>
>                 Key: CAMEL-10937
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10937
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.19.0
>
>
> So if you do
> {code}
>                 KafkaComponent kafka = new KafkaComponent();
>                 kafka.setBrokers("{{kafka.host}}:{{kafka.port}}");
> {code}
> Then those property placeholder should be resolved by Camel and set as their actual value when the component is starting up.
> Then you can configure this from just java code as well. As <bean> style have property placeholders but then its either blueprint or spring style. If we allow to use Camel style then users can do this more consistently.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)