[
https://issues.apache.org/jira/browse/CAMEL-13708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876921#comment-16876921
]
Claus Ibsen commented on CAMEL-13708:
-------------------------------------
Hmm so currently Camel's property placeholder is based on the principle of all
the properties are loaded / initialized into a combined java.util.Properties,
which are then used by the parser to find / replace placeholders with the {{ }}
syntax.
So if the idea is to have a more on-demand lookup, then we would need to work
on some new API instead to use than java.util.Properties that gets used, so we
can have something that just does as today lookup in the big
java.util.Properties and then another way to pass in something that does an
on-demand single property lookup.
> PropertiesSource to resolve a single property
> ---------------------------------------------
>
> Key: CAMEL-13708
> URL: https://issues.apache.org/jira/browse/CAMEL-13708
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Luca Burgazzoli
> Priority: Minor
> Fix For: 3.0.0
>
>
> CAMEL-13705 introduces support for property sources such as MP Config and
> others and at the moment it does require to load all the properties upfront
> on source initialization.
> It would be nice to have an additional method to resolve a single property as
> some back-and may perform some I/O to resolve properties and get alll of them
> could be expensive.
> So the properties component should:
> - leverage PropertiesSource::loadPropertiers() when is is required to know
> all the properties (i.e. when auto configure components in camel main)
> - leverage a new PropertiesSource::resolveProperty(String) when it just need
> to resolve a single property
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
