You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Ikuo YAMASAKI (JIRA)" <ji...@apache.org> on 2009/08/14 13:40:14 UTC
[jira] Created: (FELIX-1484) Dynamically bound configuration must
be reset to null after target bundle is uninstalled.
Dynamically bound configuration must be reset to null after target bundle is uninstalled.
-----------------------------------------------------------------------------------------
Key: FELIX-1484
URL: https://issues.apache.org/jira/browse/FELIX-1484
Project: Felix
Issue Type: Bug
Components: Configuration Admin
Affects Versions: configadmin-1.0.10
Reporter: Ikuo YAMASAKI
1. create a configuration with pid1 and null location.
2. bundleA, who has locationA, registers ManagedService with pid1.
3. Then the configuration MUST be "dynamically bound" to bundleA, where the
location of the configuration is set to locationA.
Here, If bundleA is uninstalled, the configuration MUST be unbound again; the
location of the configuration MUST be set to null again.
See 104.4.1 Location Binding in R4.2 cmpn
----
A null location parameter may be used to create Configuration objects that
are not bound. In this case, the objects become bound to a specific location
the first time that they are used by a bundle. When this dynamically bound
bundle is subsequently uninstalled, the Configuration object's bundle
location
must be set to null again so it can be bound again later.
----
However, the location still keeps bundleA in Felix Cm impl.
That seems a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1484) Dynamically bound configuration must
be reset to null after target bundle is uninstalled.
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned FELIX-1484:
----------------------------------------
Assignee: Felix Meschberger
> Dynamically bound configuration must be reset to null after target bundle is uninstalled.
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-1484
> URL: https://issues.apache.org/jira/browse/FELIX-1484
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.0.10
> Reporter: Ikuo YAMASAKI
> Assignee: Felix Meschberger
>
> 1. create a configuration with pid1 and null location.
> 2. bundleA, who has locationA, registers ManagedService with pid1.
> 3. Then the configuration MUST be "dynamically bound" to bundleA, where the
> location of the configuration is set to locationA.
> Here, If bundleA is uninstalled, the configuration MUST be unbound again; the
> location of the configuration MUST be set to null again.
> See 104.4.1 Location Binding in R4.2 cmpn
> ----
> A null location parameter may be used to create Configuration objects that
> are not bound. In this case, the objects become bound to a specific location
> the first time that they are used by a bundle. When this dynamically bound
> bundle is subsequently uninstalled, the Configuration object's bundle
> location
> must be set to null again so it can be bound again later.
> ----
> However, the location still keeps bundleA in Felix Cm impl.
> That seems a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1484) Dynamically bound configuration must
be reset to null after target bundle is uninstalled.
Posted by "Ikuo YAMASAKI (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743557#action_12743557 ]
Ikuo YAMASAKI commented on FELIX-1484:
--------------------------------------
I had discuss this with Felix offline and I found that my test code was not
proper: my code didn't wait after uninstallation. It should have wait for a
while because cm impl may use not SynchronousBundleListener but also
BundleListener.
However, as Felix posted, he found another related bug.
I had added the test case for OSGi-A's CT reproducing it and confirmed that felix cm impl has a
bug.
> Dynamically bound configuration must be reset to null after target bundle is uninstalled.
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-1484
> URL: https://issues.apache.org/jira/browse/FELIX-1484
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.0.10
> Reporter: Ikuo YAMASAKI
>
> 1. create a configuration with pid1 and null location.
> 2. bundleA, who has locationA, registers ManagedService with pid1.
> 3. Then the configuration MUST be "dynamically bound" to bundleA, where the
> location of the configuration is set to locationA.
> Here, If bundleA is uninstalled, the configuration MUST be unbound again; the
> location of the configuration MUST be set to null again.
> See 104.4.1 Location Binding in R4.2 cmpn
> ----
> A null location parameter may be used to create Configuration objects that
> are not bound. In this case, the objects become bound to a specific location
> the first time that they are used by a bundle. When this dynamically bound
> bundle is subsequently uninstalled, the Configuration object's bundle
> location
> must be set to null again so it can be bound again later.
> ----
> However, the location still keeps bundleA in Felix Cm impl.
> That seems a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1484) Dynamically bound configuration must
be reset to null after target bundle is uninstalled.
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743247#action_12743247 ]
Felix Meschberger commented on FELIX-1484:
------------------------------------------
Also running configadmin 1.0.10 seems to indicate this works corretly.
> Dynamically bound configuration must be reset to null after target bundle is uninstalled.
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-1484
> URL: https://issues.apache.org/jira/browse/FELIX-1484
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.0.10
> Reporter: Ikuo YAMASAKI
>
> 1. create a configuration with pid1 and null location.
> 2. bundleA, who has locationA, registers ManagedService with pid1.
> 3. Then the configuration MUST be "dynamically bound" to bundleA, where the
> location of the configuration is set to locationA.
> Here, If bundleA is uninstalled, the configuration MUST be unbound again; the
> location of the configuration MUST be set to null again.
> See 104.4.1 Location Binding in R4.2 cmpn
> ----
> A null location parameter may be used to create Configuration objects that
> are not bound. In this case, the objects become bound to a specific location
> the first time that they are used by a bundle. When this dynamically bound
> bundle is subsequently uninstalled, the Configuration object's bundle
> location
> must be set to null again so it can be bound again later.
> ----
> However, the location still keeps bundleA in Felix Cm impl.
> That seems a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1484) Dynamically bound configuration must
be reset to null after target bundle is uninstalled.
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743194#action_12743194 ]
Felix Meschberger commented on FELIX-1484:
------------------------------------------
Thanks for reporting this bug, will make up a fix soon.
> Dynamically bound configuration must be reset to null after target bundle is uninstalled.
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-1484
> URL: https://issues.apache.org/jira/browse/FELIX-1484
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.0.10
> Reporter: Ikuo YAMASAKI
>
> 1. create a configuration with pid1 and null location.
> 2. bundleA, who has locationA, registers ManagedService with pid1.
> 3. Then the configuration MUST be "dynamically bound" to bundleA, where the
> location of the configuration is set to locationA.
> Here, If bundleA is uninstalled, the configuration MUST be unbound again; the
> location of the configuration MUST be set to null again.
> See 104.4.1 Location Binding in R4.2 cmpn
> ----
> A null location parameter may be used to create Configuration objects that
> are not bound. In this case, the objects become bound to a specific location
> the first time that they are used by a bundle. When this dynamically bound
> bundle is subsequently uninstalled, the Configuration object's bundle
> location
> must be set to null again so it can be bound again later.
> ----
> However, the location still keeps bundleA in Felix Cm impl.
> That seems a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1484) Dynamically bound configuration must
be reset to null after target bundle is uninstalled.
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743243#action_12743243 ]
Felix Meschberger commented on FELIX-1484:
------------------------------------------
Added integration test ensuring bundle location is cleared after the owning bundle has been uninstalled in Rev. 804262.
Running this test on trunk shows, that this feature correctly works.
> Dynamically bound configuration must be reset to null after target bundle is uninstalled.
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-1484
> URL: https://issues.apache.org/jira/browse/FELIX-1484
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.0.10
> Reporter: Ikuo YAMASAKI
>
> 1. create a configuration with pid1 and null location.
> 2. bundleA, who has locationA, registers ManagedService with pid1.
> 3. Then the configuration MUST be "dynamically bound" to bundleA, where the
> location of the configuration is set to locationA.
> Here, If bundleA is uninstalled, the configuration MUST be unbound again; the
> location of the configuration MUST be set to null again.
> See 104.4.1 Location Binding in R4.2 cmpn
> ----
> A null location parameter may be used to create Configuration objects that
> are not bound. In this case, the objects become bound to a specific location
> the first time that they are used by a bundle. When this dynamically bound
> bundle is subsequently uninstalled, the Configuration object's bundle
> location
> must be set to null again so it can be bound again later.
> ----
> However, the location still keeps bundleA in Felix Cm impl.
> That seems a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1484) Dynamically bound configuration must be
reset to null after target bundle is uninstalled.
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-1484.
------------------------------------
Resolution: Fixed
Fix Version/s: configadmin-1.0.12
Closing this fixed. The actual implementation of fixing this is tracked in FELIX-1488
> Dynamically bound configuration must be reset to null after target bundle is uninstalled.
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-1484
> URL: https://issues.apache.org/jira/browse/FELIX-1484
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.0.10
> Reporter: Ikuo YAMASAKI
> Assignee: Felix Meschberger
> Fix For: configadmin-1.0.12
>
>
> 1. create a configuration with pid1 and null location.
> 2. bundleA, who has locationA, registers ManagedService with pid1.
> 3. Then the configuration MUST be "dynamically bound" to bundleA, where the
> location of the configuration is set to locationA.
> Here, If bundleA is uninstalled, the configuration MUST be unbound again; the
> location of the configuration MUST be set to null again.
> See 104.4.1 Location Binding in R4.2 cmpn
> ----
> A null location parameter may be used to create Configuration objects that
> are not bound. In this case, the objects become bound to a specific location
> the first time that they are used by a bundle. When this dynamically bound
> bundle is subsequently uninstalled, the Configuration object's bundle
> location
> must be set to null again so it can be bound again later.
> ----
> However, the location still keeps bundleA in Felix Cm impl.
> That seems a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1484) Dynamically bound configuration must
be reset to null after target bundle is uninstalled.
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743550#action_12743550 ]
Felix Meschberger commented on FELIX-1484:
------------------------------------------
I could reproduce the problem with these steps:
* install test bundle
* configure test bundle
* stop configuration admin service
* uninstall test bundle
* start configuration admin service
==> configuration is still bound to the uninstalled bundle
> Dynamically bound configuration must be reset to null after target bundle is uninstalled.
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-1484
> URL: https://issues.apache.org/jira/browse/FELIX-1484
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.0.10
> Reporter: Ikuo YAMASAKI
>
> 1. create a configuration with pid1 and null location.
> 2. bundleA, who has locationA, registers ManagedService with pid1.
> 3. Then the configuration MUST be "dynamically bound" to bundleA, where the
> location of the configuration is set to locationA.
> Here, If bundleA is uninstalled, the configuration MUST be unbound again; the
> location of the configuration MUST be set to null again.
> See 104.4.1 Location Binding in R4.2 cmpn
> ----
> A null location parameter may be used to create Configuration objects that
> are not bound. In this case, the objects become bound to a specific location
> the first time that they are used by a bundle. When this dynamically bound
> bundle is subsequently uninstalled, the Configuration object's bundle
> location
> must be set to null again so it can be bound again later.
> ----
> However, the location still keeps bundleA in Felix Cm impl.
> That seems a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.