| Re: [ecf-dev] Is ECF Discovery Service necessary when using RemoteServices |
> From: ecf-dev-bounces@xxxxxxxxxxx [mailto:ecf-dev-bounces@xxxxxxxxxxx] > On Behalf Of Markus Alexander Kuppe > Sent: Friday, January 14, 2011 2:50 PM > > On 01/14/2011 02:38 PM, Bartosz Czerwiński wrote: > > On the consumer side additionally I configure the container: > > IContainer container = > containerFactory.createContainer("ecf.generic.client"); > > container.connect( > > IDFactory.getDefault().createID( > > container.getConnectNamespace(), > > "ecftcp://192.168.206.1:10013/server"), null); > > Just connecting containers does not end with the remote service being > automatically added to the local service registry. This is the information I was looking for! Thank you for all replies! > > With this approach you would essentially have to retrieve all remote services > from the remote container and add them manually to the local service > registry. Pretty much what ECF remote services gives you for free anyway if > used with ECF discovery. Maybe you can help with the zoodiscovery container. When using "zoodiscovery.flavor.centralized" flavour of zoodiscovery I encounter problems with the "root node". According to the description located on the http://wiki.eclipse.org/Zoodiscovery page there should be one node which is connecting to itself. Doing this that way it causes that the node cannot connect and it's generating "Attempt connecting to ..." log entry all the time. > > Markus > _______________________________________________ > ecf-dev mailing list > ecf-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/ecf-dev
Attachment:
smime.p7s
Description: S/MIME cryptographic signature