org.omg.PortableServer
Interface ServantActivator

All Superinterfaces:

IDLEntity, LocalInterface, Object, java.io.Serializable, ServantActivatorOperations, ServantManager, ServantManagerOperations

All Known Implementing Classes:

_ServantActivatorStub

public interface ServantActivator
extends LocalInterface, ServantActivatorOperations, ServantManager, IDLEntity

When the POA has the RETAIN policy it uses servant managers that are ServantActivators.
When using such servant managers, the following statements apply for a given ObjectId used in the incarnate and etherealize operations: Servants incarnated by the servant manager will be placed in the Active Object Map with objects they have activated. Invocations of incarnate on the servant manager are serialized. Invocations of etherealize on the servant manager are serialized. Invocations of incarnate and etherealize on the servant manager are mutually exclusive.
Incarnations of a particular object may not overlap; that is, incarnate shall not be invoked with a particular ObjectId while, within the same POA, that ObjectId is in use as the ObjectId of an activated object or as the argument of a call to incarnate or etherealize that has not completed.
It should be noted that there may be a period of time between an object's deactivation and the etherealization (during which outstanding requests are being processed) in which arriving requests on that object should not be passed to its servant. During this period, requests targeted for such an object act as if the POA were in holding state until etherealize completes. If etherealize is called as a consequence of a deactivate call with an etherealize_objects parameter of TRUE, incoming requests are rejected. It should also be noted that a similar situation occurs with incarnate.
There may be a period of time after the POA invokes incarnate and before that method returns in which arriving requests bound for that object should not be passed to the servant.
A single servant manager object may be concurrently registered with multiple POAs. Invocations of incarnate and etherealize on a servant manager in the context of different POAs are not necessarily serialized or mutually exclusive. There are no assumptions made about the thread in which etherealize is invoked.

Method Summary

Methods inherited from interface org.omg.PortableServer.ServantActivatorOperations

etherealize, incarnate

Methods inherited from interface org.omg.CORBA.Object

_create_request, _create_request, _duplicate, _get_domain_managers, _get_interface_def, _get_policy, _hash, _is_a, _is_equivalent, _non_existent, _release, _request, _set_policy_override