3.7.2.2.4 Description
Object activation is triggered by a client invoking a method on
an inactive CORBA object. This causes the Portable Object Adapter
(POA) to assign a servant to the CORBA object. The
activate_object()
method is invoked before the method
invoked by the client is invoked. If activate_object()
returns successfully, that is, without raising an exception, the
requested method is executed on the servant.
The activate_object()
and
deactivate_object()
methods and the method invoked by
the client can be used by the programmer to manage object state.
The particular way these methods are used to manage object state
may vary according to the needs of the application. For a
discussion of how these methods might be used, see Creating
CORBA Server Applications.
If the object is currently infected with a global transaction,
activate_object()
executes within the scope of that
same global transaction.
It is the responsibility of the programmer of the object to
check that the stored state of the object is consistent. In other
words, it is up to the application code to save a persistent flag
that indicates whether or not deactivate_object()
successfully saved the state of the object. That flag should be
checked in activate_object()
.
Parent topic: Tobj_ServantBase:: activate_object()