You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/01/20 13:00:57 UTC
[jira] Created: (FELIX-1997) Actual configuration might not be
reflected in the web console
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.
[jira] Commented: (FELIX-1997) Actual configuration might not be
reflected in the web console
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802822#action_12802822 ]
Felix Meschberger commented on FELIX-1997:
------------------------------------------
Oh, Carsten just told me, that I was misunderstanding him.
Point is that the Apache Felix SCR is configurable through framework properties *and* configuration admin configuration but the metatype descriptor provided does not reflect the framework property state.
The fix is easy: the Apache Felix SCR bundle registers a MetaTypeProvider providing the meta type information dynamically merged from the default configuration and the framework property configuration.
> 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.
[jira] Closed: (FELIX-1997) Actual configuration might not be
reflected in the web console
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-1997.
------------------------------------
Apache Felix Declarative Services 1.6.0 has been released. The issues are now closed.
> 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
> Assignee: Carsten Ziegeler
> Fix For: scr-1.6.0
>
>
> 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.
[jira] Updated: (FELIX-1997) Actual configuration might not be
reflected in the web console
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated FELIX-1997:
------------------------------------
Fix Version/s: scr-1.4.2
I've committed a first version of a dynamic meta type provider with revision 901223.
I'll leave this issue open for further testing and possible improvements.
> 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
> Assignee: Carsten Ziegeler
> Fix For: scr-1.4.2
>
>
> 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.
[jira] Resolved: (FELIX-1997) Actual configuration might not be
reflected in the web console
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-1997.
--------------------------------------
Resolution: Fixed
I think we can resolve this for now.
If new requirements or bugs come up, we can create a new issue.
> 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
> Assignee: Carsten Ziegeler
> Fix For: scr-1.4.2
>
>
> 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.
[jira] Commented: (FELIX-1997) Actual configuration might not be
reflected in the web console
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802815#action_12802815 ]
Carsten Ziegeler commented on FELIX-1997:
-----------------------------------------
I'm not sure if this is a web console problem - the web console does not know if a service uses framework properties if no configuration is available.
Some might others don't - so I think this can't be solved in general in the web console.
Maybe another solution would be that the scr bundle creates the metatype information dynamically.
> 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.
[jira] Assigned: (FELIX-1997) Actual configuration might not be
reflected in the web console
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reassigned FELIX-1997:
---------------------------------------
Assignee: Carsten Ziegeler
> 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
> Assignee: 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.
[jira] Commented: (FELIX-1997) Actual configuration might not be
reflected in the web console
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (FELIX-1997) Actual configuration might not be
reflected in the web console
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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.