If the updated service properties do not change the status of the service as a target service, there is nothing to be done.
While it might be ok to rebind the service if the reference is dynamic, it is not ok if the reference is static. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: Felix Meschberger <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 2009/11/05 13:09 Subject: [osgi-dev] [DS] How to react to ServiceEvent.MODIFIED event Sent by: [email protected] Hi, In the latest DS specification (1.1 in Compendium 4.2) I can only find limited information on how a DS implementation is intended to react to ServiceEvent.MODIFIED event: If a service registration is modified and ceases to be a target service, the binding has to be broken. But what happens if a service registration changes without the service ceasing to be a target for the component ? My first impression would be that we would have to re-bind the service to inform the component that the registration has changed -- the component might use some service registration properties for some tasks ... (e.g. a servlet registration). For example in the Felix implementation we (intend to) unbind the service and bind it again. But there are some problems with this implementation (see FELIX-1841[1]). Thanks for any information. Regards Felix [1] https://issues.apache.org/jira/browse/FELIX-1841 _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
