Community
Participate
Working Groups
The OSGi service registry semantics map 1:1 to ECF's IDiscoveryAdvertiser. Thus, support the use case where an IServiceInfo instance is registered with the OSGi service registry to be advertised by _all_ discovery advertisers. Once unregistered, the IDAs stop advertising the service too. This has the added benefit, that users of IDiscoveryAdvertisers do not have to care about the life-cycle of IDAs.
https://git.eclipse.org/r/19861
Released to master with commit id 695a5cee6021806d7d8a05b106ee7baec3073bf8 [1] [1] http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/commit/?id=695a5cee6021806d7d8a05b106ee7baec3073bf8
JmDNS, jSLP and ZooKeeper tests all come in green, marking as fixed. :-) Btw. ECF discovery additionally could even go beyond announcing IServiceInfos transparently via whiteboard pattern in that regular OSGi services with a marker property (similar to service.exported.interfaces) could transparently be advertised (no need for IServiceInfo at all).
done
Noteworhty: "IServiceInfo instances registered with the OSGi service registry will automatically be advertised by ECF discover (if a discovery provider is active). Service Registry de-registration of IServiceInfo also de-advertises the service on the discovery layer"
(In reply to Markus Kuppe from comment #5) > Noteworhty: "IServiceInfo instances registered with the OSGi service > registry will automatically be advertised by ECF discover (if a discovery > provider is active). Service Registry de-registration of IServiceInfo also > de-advertises the service on the discovery layer" Scratch comment #5 Noteworhty: "IServiceInfo instances registered with the OSGi service registry will automatically be advertised by all (active) ECF discovery providers. Conversely Service Registry de-registration of IServiceInfo also de-advertises the service on the discovery layer".
