Hi Marek, The local Discovery service is really just a facade over statically configured remote-services.xml files. This local version exposes the same whiteboard-based interaction model as the full-on distributed Discovery service, so as to allow the core dOSGi code interact with both in the same way.
To avoid static configuration, what you'd really need is a distributed implementation of the Discovery service that would allow for dynamic publication and retrieval. Now, a reference implementation of the distibruted Discovery service has been completed by some fellow members of the OSGi Enterprise Expert Group, a group from Siemens AG. They are in the process of donating this RI to open source, so it will be available for use some time soon. Cheers, Eoghan 2009/3/26 rotgier <[email protected]> > > Hello, > > I managed to correctly deploy and run the Greeter sample from Distributed > OSGI. However the sample does not use the ServiceDiscovery thus forcing to > hardcoding the WS address on both server and client side. Looking into > dosgi > source code I found the implementation of LocalServiceDiscovery. I was > wondering if it is possible to use this Discovery (or maybe some other > stuff > from dosgi) to automagically propagate the Service from one OSGI container > to the other without specifing the WS address on the client side. > > Thanks in advance for any response. > > Kind Regards, > > Marek Psiuk > -- > View this message in context: > http://www.nabble.com/Distributed-OSGI-Service-Discovery-tp22726803p22726803.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
