|Bonobo Activation API Reference Manual|
This section describes the format of the
used by applications to tell the Bonobo Activation daemon about the
interfaces they support.
Here follows a simple example of a minimalist
<oaf_info> <oaf_server iid="OAFIID:Bonobo_CosNaming_NamingContext" type="exe" location="/usr/lib/bonobo-activation/bonobo-activation-server"> </oaf_server> </oaf_info>
oaf_server entry conventionally has three mandatory
iid (the FAQ of the Bonobo API reference manual
explains how to create an iid),
type (can be exe,
factory, or shlib) and
If the type is exe, location is
the name of the executable which creates the CORBA interfaces associated to
this entry and registers them to Bonobo Activation.
If the type is factory, location
is the iid of the component which can create the corresponding CORBA
If the type is shlib, location is
the name of the library the code is in:
Don't include the
.so suffix common on Linux
systems in the location of a
Here follows a simple example of a component activated through a factory:
<oaf_info> <oaf_server iid="OAFIID:Bonobo_Sample_Echo_Factory" type="exe" location="/usr/lib/bonobo-2.0/samples/bonobo-echo-2"> </oaf_server> <oaf_server iid="OAFIID:Bonobo_Sample_Echo" type="factory" location="OAFIID:Bonobo_Sample_Echo_Factory"> </oaf_server> </oaf_info>
If you ask Bonobo Activation to activate the
Bonobo Activation will first check if it is a factory, make sure the
corresponding factory compoenent is running (by activating it. Here,
activating the factory component is a matter of launching the executable)
create on the factory.
It will return you that object.