[
https://issues.apache.org/jira/browse/CAMEL-14218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16982737#comment-16982737
]
Claus Ibsen edited comment on CAMEL-14218 at 11/27/19 4:03 AM:
---------------------------------------------------------------
For Camel 3 - That is only supported when you configure via spring boot /
camel-main etc via properties.
For direct Java configuration via Java API then there is a JIRA ticket
(CAMEL-13807) about a "component fluent builder" alike endpoint-dsl. We need
that for this kind of configuration, where each option would then be
configurable via property placeholders and as well via their type - just as
endpoint dsl.
So for Camel 3.1 it would be cool to have component configuration fluent
builders auto-generated like endpoint dsl. We can drop that into the same JAR
camel-endpointdsl.
was (Author: davsclaus):
For Camel 3 - That is only supported when you configure via spring boot /
camel-main etc via properties.
For direct Java configuration via Java API then there is a JIRA ticket about a
"component fluent builder" alike endpoint-dsl. We need that for this kind of
configuration, where each option would then be configurable via property
placeholders and as well via their type - just as endpoint dsl.
So for Camel 3.1 it would be cool to have component configuration fluent
builders auto-generated like endpoint dsl. We can drop that into the same JAR
camel-endpointdsl.
> Property placeholders on component setters fail to replace values
> ------------------------------------------------------------------
>
> Key: CAMEL-14218
> URL: https://issues.apache.org/jira/browse/CAMEL-14218
> Project: Camel
> Issue Type: Bug
> Reporter: Omar Al-Safi
> Priority: Minor
>
> Related to CAMEL-10937, now if we have the same example as CAMEL-10937:
> {code}
> KafkaComponent kafka = new KafkaComponent();
> kafka.setBrokers("{{kafka.host}}:{{kafka.port}}");
> {code}
> Having the properties component injected, looks camel is not resolving the
> placeholder for these properties. However, since the property binding has
> been heavily reworked in 3.0.0, I wasn't sure if that is an expected behavior
> or a bug, perhaps [~davsclaus] you can shed some light here?
> In case it needs to be fixed, I'd like to help out to fix it :).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
