Defines a C++ plug‑in to be installed during communicator initialization. The
basename and optional
version components are used to construct the name of a DLL or shared library. If no version is supplied, the Ice version is used. The
function component is the name of a function with C linkage. For example, the entry point
MyPlugin,33:create would imply a shared library name of
libMyPlugin.so.33 on Unix and
MyPlugin33.dll on Windows. Furthermore, if Ice is built on Windows with debugging, a
d is automatically appended to the version (for example,
MyPlugin33d.dll).
Defines a Java plug‑in to be installed during communicator initialization. The specified class must implement the
Ice.PluginFactory interface. Any arguments that follow the class name are passed to the
create method. For example:
Defines a .NET plug‑in to be installed during communicator initialization. The assembly can be the full assembly name, such as
myplugin, Version=0.0.0.0, Culture=neutral, or an assembly DLL name such as
myplugin.dll. The specified class must implement the
Ice.PluginFactory interface. Any arguments that follow the class name are passed to the
create method. For example:
Defines a plug‑in to be installed during communicator initialization. The format of
entry_point varies by Ice implementation language, therefore this property cannot be defined in a configuration file that is shared by programs in different languages. Ice provides an alternate syntax that facilitates such sharing:
Determines the order in which plug‑ins are loaded. The Ice run time loads the plug‑ins in the order they appear in
names, where each plug‑in name is separated by a comma or white space. Any plug‑ins not mentioned in
names are loaded afterward, in an undefined order.
If num is a value greater than zero, the Ice run time automatically initializes the plug‑ins it has loaded. The order in which plug‑ins are loaded and initialized is determined by
Ice.PluginLoadOrder. An application may need to set this property to zero in order to interact directly with a plug‑in after it has been loaded but before it is initialized. In this case, the application must invoke
initializePlugins on the plug‑in manager to complete the initialization process. If not defined, the default value is 1.
