[
https://issues.apache.org/jira/browse/FELIX-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802810#action_12802810
]
Felix Meschberger commented on FELIX-1997:
------------------------------------------
I assume this is a web console issue....
As for the configuration: The Web Console uses the current configuration (if
available) or the configuration from the Metatype Service as the contents for
the configuration form. For now, the Web Console does not take any framework
properties into consideration.
It could of course be implemented, that in the absence of a Configuration Admin
configuration, any Metatype servcie property might be "overwritten" by
framework properties. The problem, of course is, that not all configuration
users support framework properties. So this has the danger of not reflecting
reality, too.
> Actual configuration might not be reflected in the web console
> --------------------------------------------------------------
>
> Key: FELIX-1997
> URL: https://issues.apache.org/jira/browse/FELIX-1997
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.4.0
> Reporter: Carsten Ziegeler
>
> If no configuration exists in the config admin, a default configuration is
> used which is derived from framework properties.
> If these properties do not match the default settings, than the configuration
> view in the web console shows the wrong default settings - and not the
> settings that are currently used.
> One possible solution to fix this might be to create a configuration if the
> framework properties do not match the default settings
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
