You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Valentin Valchev (JIRA)" <ji...@apache.org> on 2010/03/22 10:32:27 UTC

[jira] Resolved: (FELIX-1996) Console should warn when config is bound to a different bundle

     [ 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.