[
https://issues.apache.org/jira/browse/FELIX-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488920#comment-17488920
]
Carsten Ziegeler commented on FELIX-6503:
-----------------------------------------
I didn't want to overload the UI and leave it up to the user to decide. But
obviously this makes the assumption that every client of a configuration can
handle partial configurations (where default values are missing).
I can't see a good way out, the first one coming to my mind is a switch for the
web console to either work like before or with the new way.
> 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)
