[
https://issues.apache.org/jira/browse/FELIX-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802820#action_12802820
]
Felix Meschberger commented on FELIX-1997:
------------------------------------------
> Maybe another solution would be that the scr bundle creates the metatype
> information dynamically.
Probably not, because SCR does not know anything about metatype properties
provided by the bundles. Its none of the business of the SCR: SCR just takes
the descriptors merges in any configuration admin configuration (and
ComponentFactory.newInstance properties in the ComponentFactory case) and gives
this to the component.
It is up to the component to configure itself from the provided properties and
the framework properties.
But, the bundle providing the component could do that. For example the Web
Console main servlet itself registers a MetaTypeProvider service providing
dynamic information (the use case is dyanimcally generating the plugins to
enable or disable).
> 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.
