Yes, it's not the purpose of the Ice.Default.Host property to define the endpoints of object adapters (and therefore the interfaces the object adapter will listen to). See the description of this property in the Appendix C.7 of the Ice manual for more information.
If you use the createObjectAdapterWithEndpoints method to create the object adapter, you have to specify the object adapter endpoints directly in the code, for example:
Code:
Ice::ObjectAdapterPtr adapter = communicator->createObjectAdapterWithEndpoints("Machine", "tcp -p 10000 -h 192.168.0.3:tcp -p 10000 -h 1.1.0.3");
If you create the object adapter with the createObjectAdapter method, you can set the endpoints with configuration properties. For example, if you create the adapter with the following code:
Code:
Ice::ObjectAdapterPtr adapter = communicator->createObjectAdapter("Machine");
You can set the object adapter endpoints with the Machine.Endpoints property in a configuration file, for example:
Code:
Machine.Endpoints=tcp -p 10000 -h 192.168.0.3:tcp -p 10000 -h 1.1.0.3
You can turn on the network tracing (--Ice.Trace.Network=1) to make sure your server will listen on the endpoints specified either in the code or the configuration.
Benoit.