[jira] [Reopened] (KARAF-2367) Config Not Released When Declarative Services Bundle Stopped

["Gareth Collins (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KARAF-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gareth Collins reopened KARAF-2367:
-----------------------------------


Hello Guillaume,

I also said the config is not released on uninstall either.

thanks,
Gareth

> Config Not Released When Declarative Services Bundle Stopped
> ------------------------------------------------------------
>
>                 Key: KARAF-2367
>                 URL: https://issues.apache.org/jira/browse/KARAF-2367
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-config
>    Affects Versions: 2.3.1
>            Reporter: Gareth Collins
>            Assignee: Guillaume Nodet
>
> If I have a declarative services bundle which has config associated with it. i.e.:
> karaf@root> list -t 0 -s | grep myservice
> [ 234] [Active     ] [            ] [   80] com.mycompany.myservice (1.0.0.20130530-jenkins-383)
> karaf@root> config:list "(service.pid=com.mycompany.myservice)"
> ----------------------------------------------------------------
> Pid:            com.mycompany.myservice
> BundleLocation: mvn:com.mycompany/myservice/1.0.0-SNAPSHOT
> Properties:
> .
> .
> If I stop or uninstall this bundle, the config does not get released:
> karaf@root> stop 234
> karaf@root> config:list "(service.pid=com.mycompany.myservice)"
> ----------------------------------------------------------------
> Pid:            com.mycompany.myservice
> BundleLocation: mvn:com.mycompany/myservice/1.0.0-SNAPSHOT
> Properties:
> .
> .
> This is problematic because it stops you from uninstalling the bundle and installing a new bundle at a new location which will reuse the config. To get around this issue I currently must delete the old config and recreate it. This problem persists across karaf restarts.
> I know I can also do this:
> karaf@root> update 234 <new location>
> But that doesn't always work (once I can reproduce this "update" failure consistently, I will open another defect)



--
This message was sent by Atlassian JIRA
(v6.2#6252)