All Known Implementing Classes:
POAManager, POAManagerImpl
Audrius - Meskauskas, Lithuania (AudriusA@Bioinformatics.org)| Method from org.omg.PortableServer.POAManagerOperations Summary: |
|---|
| activate, deactivate, discard_requests, get_state, hold_requests |
| Method from org.omg.PortableServer.POAManagerOperations Detail: |
|---|
|
Turns the asociated POAs into inactive state. The POAs in the incative state will reject new requests. A cliet, trying to invoke an object, belonging to the inactivated POA, will receive the remote exception (org.omg.CORBA.OBJ_ADAPTER , minor code 0x535503ea, incomplete). If the POA is once inactivated, it cannot be activated again. The operation is used when the associated POAs are to be shut down. Some independent implementations may set the minor code of the OBJ_ADAPTER to 1, as recommended by OMG (formal/04-03-12). The interoperable systems should expect any of these two values. |
Turns the associated POAs into discaring state. In this state, the POAs discard the incoming requests. This mode is used in situations when the server is flooded with requests. The client receives remote exception (org.omg.CORBA.TRANSIENT , minor code 0x535503e9, incomplete). Some independent implementations may set the minor code of the TRANSIENT to 1, as recommended by OMG (formal/04-03-12). The interoperable systems should expect any of these two values. |
|
|