[
https://issues.apache.org/jira/browse/FELIX-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412814#comment-17412814
]
Stefan Feilmeier commented on FELIX-6436:
-----------------------------------------
Thank you [~cziegeler] for taking the time and the detailed reply. I was not
considering the different levels of ConfigurationAdmin and Declarative Service.
In fact in the meantime I settled with #4 and implemented measures to make sure
I consider defaults when appropriate.
[https://github.com/OpenEMS/openems/pull/1618] . This solves the problem for me
and a toggle is not required. In fact the improvement to not store defaults
might prove to be very useful for future updates. Thanks for the effort!
> Exclude default values (from metatype) in Configuration
> -------------------------------------------------------
>
> Key: FELIX-6436
> URL: https://issues.apache.org/jira/browse/FELIX-6436
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: webconsole-4.6.4
>
>
> When an OSGi configuration is changed through the web console, all properties
> are set in the created/updated configuration, including those which are
> actually not set in the web console - but where just the default value is
> transfered back.
> This prohibits those configurations from using any change in the default
> values.
> The implementation could be smarter and check metatype info (if available)
> and exclude all properties with default values.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
