[
https://issues.apache.org/jira/browse/FELIX-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488850#comment-17488850
]
Andreas Lemmer commented on FELIX-6503:
---------------------------------------
So you're actually suggesting that I must bind the metatype service in EVERY
component which has a configuration, check for the presence of REQUIRED
configuration properties, and in case of their absence, must parse the
configuration XML via Metatype to find their default value? This is absolutely
not acceptable, sorry. It worked flawlessly with webconsole 4.5.2 (didn't test
with 4.6), but with 4.7, it's broken.
> 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)
