[
https://issues.apache.org/jira/browse/FELIX-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-1488.
--------------------------------------
Resolution: Fixed
After much back and forth, it looks like we now reached kind of a consensus
(for the short-term) with respect to configuration binding:
Calling Configuration.setBundleLocation() does not cause any bound
configuration to be unbound. Neither are configurations newly bound due to this.
On the other hand further configuration updates will be sent out according to
the bundle location set. Any dynamic configuration binding prevalent to calling
setBundleLocation() is dropped (unless of course the dynamic binding is the
same as the new static binding).
So, it is confimed the current trunk state implements this as agreed upon and I
close this issue.
> 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.
