[
https://issues.apache.org/jira/browse/FELIX-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488911#comment-17488911
]
Andreas Lemmer commented on FELIX-6503:
---------------------------------------
You're probably right, although I'm still thinking that the current
implementation is wrong, because if I want to remove a configuration value or
set it to null, I would rather leave the field empty or have a checkbox to
disable the property than entering the default value and have the property
magically removed.
Can you recommend a workaround other than using an old version of Webconsole or
clone the code and reimplement the old, more correct way?
Wouldn't it be better to have both possibilities: set a value which was entered
via the form and/or remove the property by leaving the field empty or using a
checkbox?
> 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)
