[
https://issues.apache.org/jira/browse/FELIX-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488801#comment-17488801
]
Carsten Ziegeler commented on FELIX-6503:
-----------------------------------------
This is actually by design. The idea is that the configuration does not need to
contain the property with the default value as whoever is consuming the
configuration will apply the default value if the property is missing. That's
usually how configurations are consumed,
> Webconsole doesn't set configuration property to default value
> --------------------------------------------------------------
>
> Key: FELIX-6503
> URL: https://issues.apache.org/jira/browse/FELIX-6503
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-4.7.2
> Reporter: Andreas Lemmer
> Priority: Blocker
>
> After changing a configuration property in the webconsole configMgr, it
> cannot be changed back to the default value again. The webconsole shows an
> exclamation mark saying that the property was not set and the default value
> is only displayed.
> In the @Modified method, the property map doesn't contain the property key.
> It seems that instead of setting the entered value (which happens to be equal
> to the default value), the configuration property is just removed.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
