Hi Ivan Is this failing for you when you run the itest as is or are you running the separate parts of the test manually?
The contents of the client/server-config.xml file were inveted by Tuscany. They are aren't defined in the specifications. We needed somechere to hold configuration that determines what the the default protocol configuration for remote bindings is and what the default domain and domain registry URI were. There has been some discussion recently about the utility and form of the domain and registry URIs so I expect they will be changed but in the code at the moment, and in this test in particular, you can see that domain registry uri is being used to specify configuration for the distributed registry that's used under the covers to copy endpoint information between JVMs. This particular test is configured to use the Tribes software to do this for us. It's based on discovering remote nodes using multicast so it should work without specific configuration assuming that you have multicast enabled. There is a similar test configured to use Hazelcast. Regards Simon
