During the creation of a communicator, the Ice run time initializes a number of features that affect the communicator’s operation. Once set, these features remain in effect for the life time of the communicator, that is, you cannot change these features after you have created a communicator. Therefore, if you want to customize these features, you must do so when you create the communicator.
To establish these features, you initialize a structure or class of type InitializationData with the relevant settings. For C++ the structure is defined as follows:
For languages other than C++, InitializationData is a class with all data members public. (The string converter fields are missing for these languages.)
For C++, Ice::initialize is overloaded as follows:
The version of initialize that accepts an
argc/
argv pair looks for Ice-specific command-line options and removes them from the argument vector, as described on
page 276. The version without an
argc/
argv pair is useful if you want to prevent property settings for a program from being changed by command- line arguments (see
Section 30.8).
To set a feature, you set the corresponding field in the InitializationData structure and pass the structure to
initialize. For example, to establish a custom logger of type
MyLogger, you can use:
For Java, C#, and Objective‑C,
Ice.Util.initialize is overloaded similarly
1 (as is
Ice.initialize for Python and
Ice::initialize for Ruby), so you can pass an
InitializationData instance either with or without an argument vector. Note that you must supply an argument vector if you want
initialize to look for a configuration file in the
ICE_CONFIG environment variable. (See also
Section 30.6.)