org.omg.PortableServer

Class ServantLocatorPOA

  • All Implemented Interfaces:
    InvokeHandler, ServantLocatorOperations, ServantManagerOperations

    public abstract class ServantLocatorPOA
    extends Servant
    implements ServantLocatorOperations, InvokeHandler
    When the POA has the NON_RETAIN policy it uses servant managers that are ServantLocators. Because the POA knows that the servant returned by this servant manager will be used only for a single request, it can supply extra information to the servant manager's operations and the servant manager's pair of operations may be able to cooperate to do something different than a ServantActivator. When the POA uses the ServantLocator interface, immediately after performing the operation invocation on the servant returned by preinvoke, the POA will invoke postinvoke on the servant manager, passing the ObjectId value and the Servant value as parameters (among others). This feature may be used to force every request for objects associated with a POA to be mediated by the servant manager.
    • Constructor Detail

      • ServantLocatorPOA

        public ServantLocatorPOA()
    • Method Detail

      • _invoke

        public OutputStream _invoke(String $method,
                           InputStream in,
                           ResponseHandler $rh)
        Description copied from interface: InvokeHandler
        Invoked by the ORB to dispatch a request to the servant. ORB passes the method name, an InputStream containing the marshalled arguments, and a ResponseHandler which the servant uses to construct a proper reply. Only CORBA SystemException may be thrown by this method. The method must return an OutputStream created by the ResponseHandler which contains the marshalled reply. A servant must not retain a reference to the ResponseHandler beyond the lifetime of a method invocation. Servant behaviour is defined as follows:

        1. Determine correct method, and unmarshal parameters from InputStream.

        2. Invoke method implementation.

        3. If no user exception, create a normal reply using ResponseHandler.

        4. If user exception occurred, create exception reply using ResponseHandler.

        5. Marshal reply into OutputStream returned by ResponseHandler.

        6. Return OutputStream to ORB.

        Specified by:
        _invoke in interface InvokeHandler
        Parameters:
        $method - The method name.
        in - The InputStream containing the marshalled arguments.
        $rh - The ResponseHandler which the servant uses to construct a proper reply
        Returns:
        The OutputStream created by the ResponseHandler which contains the marshalled reply
      • _all_interfaces

        public String[] _all_interfaces(POA poa,
                               byte[] objectId)
        Description copied from class: Servant
        Used by the ORB to obtain complete type information from the servant.
        Specified by:
        _all_interfaces in class Servant
        Parameters:
        poa - POA with which the servant is associated.
        objectId - is the id corresponding to the object associated with this servant.
        Returns:
        list of type information for the object.

Document created the 11/06/2005, last modified the 04/03/2020
Source of the printed document:https://www.gaudry.be/en/java-api-rf-org/omg/portableserver/servantlocatorpoa.html/.html/

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:fr Manuel PHP : https://docs.oracle.com

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut