[jira] [Commented] (FELIX-4852) Unbinding configuration does not have desired effect

["David Jencks (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496156#comment-14496156 ] 

David Jencks commented on FELIX-4852:
-------------------------------------

Setting it to null allows rebinding to a different bundle if the one that originally bound it doesn't clean up properly after itself.  You seem to be proposing a way to provide a new "disabled" state for configurations?  I would at least consider directly adding a disabled state to felix config admin and if it seems useful enough proposing an RFC.

> Unbinding configuration does not have desired effect
> ----------------------------------------------------
>
>                 Key: FELIX-4852
>                 URL: https://issues.apache.org/jira/browse/FELIX-4852
>             Project: Felix
>          Issue Type: Improvement
>          Components: Web Console
>    Affects Versions: webconsole-4.2.8
>            Reporter: Carsten Ziegeler
>             Fix For: webconsole-4.2.10
>
>
> The configuration plugin for the web console supports unbinding a configuration - which calls setBundleLocation(null) on the configuration object.
> However, this usually has no effect as the configuration is picked up by the same managed service once the configuration gets available/free. This results in rebinding the config and then it's not unbound anymore.
> A workaround right now is to specify an invalid location string in the text field..
> However, maybe we can set a special value instead of null for the location and also when displaying it, displaying it as unbound - an invalid bundle name should do



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)