Closed bjhargrave closed 12 years ago
Comment author: schnabel@us.ibm.com
with SCR 1.1, components can be registered with a "modified" method, so that they can accept config updates without deactivating/reactivating the component. The problem is that a config refresh updates the properties of the ServiceReference as well. Changes to the properties of a ServiceReference cause the service to be rebound to other components that depend on the "modified" service. There is no way to specify (with the current "reference" xml) that changes to the service properties of the injected reference are acceptable, or to notify the "receiving" component that the service properties of an injected reference changed aside from doing the rebind (which could end up with double registration, if you're optional/multiple and not watching your instances).
I did talk to Peter about this, he suggested I open the bug.
Felix DS dealt with this:
https://issues.apache.org/jira/browse/FELIX-1841 https://issues.apache.org/jira/browse/FELIX-1893
Comment author: @bjhargrave
This was already filed in publicbug BZ#63: https://www.osgi.org/bugzilla/show_bug.cgi?id=63
Comment author: Alasdair Nottingham <not@uk.ibm.com>
I was a little confused when reading this bug and FELIX-1841. So having spoken to BJ I just thought I would add a clarification. The statement:
Changes to the properties of a ServiceReference cause the service to be rebound to other components that depend on the "modified" service.
relate to a bug in felix SCR (1841 specifically) and not a bug in the DS 1.1 specification.
Comment author: @bjhargrave
RFC 176 was approved and has been incorporated in the latest Compendium draft spec.
Original bug ID: BZ#1956 From: schnabel@us.ibm.com Reported version: R4 V4.2