You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2010/01/19 17:06:54 UTC
[jira] Created: (FELIX-1996) Console should warn when config is
bound to a different bundle
Console should warn when config is bound to a different bundle
--------------------------------------------------------------
Key: FELIX-1996
URL: https://issues.apache.org/jira/browse/FELIX-1996
Project: Felix
Issue Type: Improvement
Components: Web Console
Affects Versions: webconsole-2.0.4
Reporter: Bertrand Delacretaz
Priority: Minor
Working on upgrades of an OSGi-based system, which include moving services from one bundle to another for refactoring purposes, I had several cases where the console didn't display configuration values correctly, because the configuration was bound to a different bundle (B) than the one (A) where the corresponding service comes from.
Usually because the service that uses the config used to be in bundle A, but was moved to bundle B.
The symptoms are either no fields or values shown on the configuration page at all, or all name/value pairs displayed in a single textarea instead of individual fields.
IIUC that's because the webconsole cannot access the metadata about the configuration fields anymore in this case.
If that's correct, it would be good to have a warning on the configuration page when that happens, to help troubleshooting such cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1996) Console should warn when config is
bound to a different bundle
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841261#action_12841261 ]
Felix Meschberger commented on FELIX-1996:
------------------------------------------
Actually, if the boundle with the bundle location to which the configuration is bound has been uninstalled, the configuration admin support of the current (Rev. 918988) trunk locates another bundle providing a description of the configuration. If found, that description is used to render the configuration.
Thus, it makes sense, that in such a situation the bundle has been uninstalled and re-installed with a different bundle location. Thus informing about the bundle location mismatch makes perfect sense.
The user can then still unbind the configuration from the old location and then save the configuration to have it bound to the bundle at the new location.
> Console should warn when config is bound to a different bundle
> --------------------------------------------------------------
>
> Key: FELIX-1996
> URL: https://issues.apache.org/jira/browse/FELIX-1996
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-2.0.4
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> Working on upgrades of an OSGi-based system, which include moving services from one bundle to another for refactoring purposes, I had several cases where the console didn't display configuration values correctly, because the configuration was bound to a different bundle (B) than the one (A) where the corresponding service comes from.
> Usually because the service that uses the config used to be in bundle A, but was moved to bundle B.
> The symptoms are either no fields or values shown on the configuration page at all, or all name/value pairs displayed in a single textarea instead of individual fields.
> IIUC that's because the webconsole cannot access the metadata about the configuration fields anymore in this case.
> If that's correct, it would be good to have a warning on the configuration page when that happens, to help troubleshooting such cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1996) Console should warn when config is
bound to a different bundle
Posted by "Valentin Valchev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Valchev reassigned FELIX-1996:
---------------------------------------
Assignee: Valentin Valchev
> Console should warn when config is bound to a different bundle
> --------------------------------------------------------------
>
> Key: FELIX-1996
> URL: https://issues.apache.org/jira/browse/FELIX-1996
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-2.0.4
> Reporter: Bertrand Delacretaz
> Assignee: Valentin Valchev
> Priority: Minor
>
> Working on upgrades of an OSGi-based system, which include moving services from one bundle to another for refactoring purposes, I had several cases where the console didn't display configuration values correctly, because the configuration was bound to a different bundle (B) than the one (A) where the corresponding service comes from.
> Usually because the service that uses the config used to be in bundle A, but was moved to bundle B.
> The symptoms are either no fields or values shown on the configuration page at all, or all name/value pairs displayed in a single textarea instead of individual fields.
> IIUC that's because the webconsole cannot access the metadata about the configuration fields anymore in this case.
> If that's correct, it would be good to have a warning on the configuration page when that happens, to help troubleshooting such cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1996) Console should warn when config is
bound to a different bundle
Posted by "Valentin Valchev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847403#action_12847403 ]
Valentin Valchev commented on FELIX-1996:
-----------------------------------------
So let's say for a PID:
- location1 = ManagedService.reference.getBundle().getLocation();
- location2 = configuration.getLocation();
if (location1 != location2) warnUser();
-----
If this is correct, then it should be fairly easy to solve that issue and we can schedule it for 3.0.0 release. I'll try to provide a patch next Monday.
> Console should warn when config is bound to a different bundle
> --------------------------------------------------------------
>
> Key: FELIX-1996
> URL: https://issues.apache.org/jira/browse/FELIX-1996
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-2.0.4
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> Working on upgrades of an OSGi-based system, which include moving services from one bundle to another for refactoring purposes, I had several cases where the console didn't display configuration values correctly, because the configuration was bound to a different bundle (B) than the one (A) where the corresponding service comes from.
> Usually because the service that uses the config used to be in bundle A, but was moved to bundle B.
> The symptoms are either no fields or values shown on the configuration page at all, or all name/value pairs displayed in a single textarea instead of individual fields.
> IIUC that's because the webconsole cannot access the metadata about the configuration fields anymore in this case.
> If that's correct, it would be good to have a warning on the configuration page when that happens, to help troubleshooting such cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1996) Console should warn when config is
bound to a different bundle
Posted by "Valentin Valchev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Valchev resolved FELIX-1996.
-------------------------------------
Resolution: Fixed
Fix Version/s: webconsole-3.0.0
Now, when you open the configuration for editing at the top of the dialog is shown an error message with description of the problem.
> Console should warn when config is bound to a different bundle
> --------------------------------------------------------------
>
> Key: FELIX-1996
> URL: https://issues.apache.org/jira/browse/FELIX-1996
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-2.0.4
> Reporter: Bertrand Delacretaz
> Assignee: Valentin Valchev
> Priority: Minor
> Fix For: webconsole-3.0.0
>
>
> Working on upgrades of an OSGi-based system, which include moving services from one bundle to another for refactoring purposes, I had several cases where the console didn't display configuration values correctly, because the configuration was bound to a different bundle (B) than the one (A) where the corresponding service comes from.
> Usually because the service that uses the config used to be in bundle A, but was moved to bundle B.
> The symptoms are either no fields or values shown on the configuration page at all, or all name/value pairs displayed in a single textarea instead of individual fields.
> IIUC that's because the webconsole cannot access the metadata about the configuration fields anymore in this case.
> If that's correct, it would be good to have a warning on the configuration page when that happens, to help troubleshooting such cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1996) Console should warn when config is
bound to a different bundle
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed FELIX-1996.
-----------------------------------
> Console should warn when config is bound to a different bundle
> --------------------------------------------------------------
>
> Key: FELIX-1996
> URL: https://issues.apache.org/jira/browse/FELIX-1996
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-2.0.4
> Reporter: Bertrand Delacretaz
> Assignee: Valentin Valchev
> Priority: Minor
> Fix For: webconsole-3.0.0
>
>
> Working on upgrades of an OSGi-based system, which include moving services from one bundle to another for refactoring purposes, I had several cases where the console didn't display configuration values correctly, because the configuration was bound to a different bundle (B) than the one (A) where the corresponding service comes from.
> Usually because the service that uses the config used to be in bundle A, but was moved to bundle B.
> The symptoms are either no fields or values shown on the configuration page at all, or all name/value pairs displayed in a single textarea instead of individual fields.
> IIUC that's because the webconsole cannot access the metadata about the configuration fields anymore in this case.
> If that's correct, it would be good to have a warning on the configuration page when that happens, to help troubleshooting such cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.