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