[
https://issues.apache.org/jira/browse/DELTASPIKE-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951033#comment-15951033
]
Mark Struberg commented on DELTASPIKE-1212:
-------------------------------------------
I think this is not an accident but by design. If you use getAllProperties then
you cannot easily make assumptions about whether a specific
property-evaluation, projectstage-evaluation or variable replacement is to be
assumed. Any assumption we would take might be wrong, isn't?
One could still iterate over the keys and resolve them one by one.
> Introduce a ConfigResolver.resolveAllProperties method
> ------------------------------------------------------
>
> Key: DELTASPIKE-1212
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1212
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Configuration
> Affects Versions: 1.7.0
> Reporter: John D. Ament
> Fix For: 1.8.0
>
>
> Invoking ConfigResolver.getAllProperties does not expand out any inlined
> variables. In addition, assume the following properties file and project
> stage = Development
> {code}
> some-service-url=${edge-server-url}/some-service
> edge-server-url=undefined
> edge-server-url.Development=http://development:8081
> edge-server-url.Staging=http://staging:8081
> edge-server-url.Production=http://prod:8081
> {code}
> calling {{getAllProperties}} returns the raw output of this file.
> Introducing a new {{resolveAllProperties}} method would only return back the
> active values. The expected result would be
> {code}
> some-service-url=http://development:8081/some-service
> edge-server-url=http://development:8081
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
