[ 
https://issues.apache.org/jira/browse/FELIX-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved FELIX-6590.
-------------------------------------
    Resolution: Fixed

Fixed in 
https://github.com/apache/felix-dev/commit/1bdd64eff5cd818f31953e193f49014c3124d968
 by invoking replace on the directives
Added test case based on the use case from the description

> [Interprolator Plugin] cascading defaults error
> -----------------------------------------------
>
>                 Key: FELIX-6590
>                 URL: https://issues.apache.org/jira/browse/FELIX-6590
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin
>    Affects Versions: configadmin-interpolation-plugin-1.2.6
>            Reporter: Jürgen Albert
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: configadmin-interpolation-plugin-1.2.8
>
>
> I have the following construct:
> $[env:MQTT_WRITE_HOST;default='$[prop:MQTT_WRITE_HOST;default=some.host]']
> The Goal is, env -> prop -> default
> The result unfortunately is not as expected. if I have no default for the 
> props statement, the fallback works and it tries to resolve the property if 
> the env is not set. If I have the second default for the case that nothing is 
> set, the env immediately defaults to  "some.host]".
> The Quotes for the default make no difference in this case, even if I only 
> quote the value of the last default. My current workaround is 
> $[env:MQTT_WRITE_HOST;default=]$[prop:MQTT_WRITE_HOST;default=some.host]
> Additionally a convinient version like propEnv and envProp would be nice to 
> cover suche a case in on statement.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to