felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1488) Configuration binding is broken
Date Thu, 20 Aug 2009 08:16:14 GMT

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

Felix Meschberger commented on FELIX-1488:

In Rev. 806074/806078 (integration tests) and 806075 (implementation) I disabled the automatic
reassignment of configurations if the static bundle location is set to a different location.

For the integration tests, the code is guarded by a switch to change either one or the other
expected behaviour of reassignment.

For the implementation the main reassignment code has just been commented out.

In Rev. 806083 I added the removal of dynamic bundle location binding if the static locaiton
is set to a location different than the current dynamic binding.

> Configuration binding is broken
> -------------------------------
>                 Key: FELIX-1488
>                 URL: https://issues.apache.org/jira/browse/FELIX-1488
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin
>    Affects Versions: configadmin-1.0.10
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: configadmin-1.0.12
> Configuration can be statically or dynamically bound:
>  * A configuration is statically bound by explicitly calling the Configuration.setBundleLocation
method or
>     by creating the configuration object with a non-null bundle location. Static binding
must be persisted and
>     is only reset by explicitly calling the setBundleLocation with a null argument.
>  * A configuration may dynamically bound if the configuration has been created with a
null bundle location and
>     the setBundleLocation has not been called (or called with a null argument). If such
an unbound configuration
>     is provided to a ManagedService[Factory] it is dynamically bound to the service's
bundle. Such bundle
>     binding is not persisted.
> The reason why dynamic binding need not be persisted is actually an implementation detail
because we keep used configurations in an internal cache. Entries in the cache are only removed
if the configuration is deleted or if the configuration admin service is stopped. In the first
case, bundle binding is lost anyway. In the second case dynamic bundle bindings will be recreated
on configuration admin service restart when the configurations are supplied to ManagedService[Factory]
services again.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message