CORBA Programming Reference
|
 |
 |
|
 |
 |
PortableServer::Current::get_POA
Synopsis
Returns a reference to the POA implementing the object in whose context it is called.
C++ Binding
POA_ptr get_POA ();
Argument
Exceptions
If this operation is called outside the context of a POA-dispatched operation, a PortableServer::NoContext exception is raised.
Description
This operation returns a reference to the POA implementing the object in whose context it is called.
Note: This function is supported only for a joint client/server.
Return Values
This operation returns a reference to the POA implementing the object in whose context it is called.
POAManager Member Functions
Each POA object has an associated POAManager object. A POAManager may be associated with one or more POA objects. A POAManager encapsulates the processing state of the POAs with which it is associated. Using operations on the POA manager, an application can cause requests for those POAs to be queued or discarded, and can cause the POAs to be deactivated.
POA managers are created and destroyed implicitly. Unless an explicit POAManager object is provided at POA creation time, a POAManager is created when a POA is created and is automatically associated with that POA. A POAManager object is implicitly destroyed when all of its associated POAs have been destroyed.
A POAmanager has four possible processing states: active, inactive, holding, and discarding. The processing state determines the capabilities of the associated POAs and the disposition of requests received by those POAs.
A POAmanager is created in the holding state. In that state, any invocations on its POA are queued until the POA manager enters the active state. This version of BEA Tuxedo supports only the ability to enter active and inactive states. That is, this version does not support the ability to return to holding state or to enter discarding state.
