***  This package contains classes that provide Binary Compatibility only, not Source Compatibility  ***

Note:
Extension of the classes in this package is prohibited unless otherwise documented. Similarly, extension or implementation of the interfaces in this package is prohibited except as documented.

Package com.sas.net.rmi

The com.sas.net.rmi package provides networking components dealing with Java Remote Method Invocation (RMI).

See:
          Description

Interface Summary
RemoteObjectExporterInterface Interface designating methods associated with exporting/unexporting a remote object to the RMI system.
RMIExportConfiguration Interface that describes a configuration for exporting a remote object to the RMI system.
 

Class Summary
AbstractRemoteObjectExporter An abstract base class providing base implementations to export/unexport a remote object to/from the RMI system.
ActivatableExporter Utility class used to export/unexport an activatable remote object to/from the RMI system using Constants Constants denoting standard port numbers used by SAS applications employing remote RMI objects.
UnicastRemoteObjectExporter Utility class used to export/unexport a unicast remote object to/from the RMI system using

Package com.sas.net.rmi Description

The com.sas.net.rmi package provides networking components dealing with Java Remote Method Invocation (RMI).

Overview

A Java remote object may be implicitly exported to the RMI system if its class extends UnicastRemoteObject or it may be explicitly exported/unexported using a utility method such as UnicastRemoteObject.exportObject(java.rmi.Remote remote, int port, java.rmi.server.RMIClientSocketFactory rmiClientSocketFactory, java.rmi.server.RMIServerSocketFactory rmiServerSocketFactory). A UnicastRemoteObject will automatically export the remote object to the RMI system at construction time. If you have a remote object implementation that cannot subclass a standard remote object implementation such as UnicastRemoteObject because your class must extend another class, then the RMI export utilities provided by this API may be useful to provide a standard mechanism to export/unexport your remote object. If your remote object implementation can extend a standard remote object implementation then there is no benefit to using this API's exporter utilities unless you want to be able to control whether or not your object is exported to the RMI system.

If one desires to provide a single implementation which is desired to be remotely accessed in one usage scenario or just locally accessed in another usage scenario, then consider using of the export utilities provided by this package. This API provides convenience utilities to provide explicit RMI export capabilities for the case where an implicit export is not being employed. These utilities are only intended for use by an implementation which needs to control whether or not an object is exported to the RMI system.

Note that if your remote object implementation does not extend a standard remote object implementation such as UnicastRemoteObject, then your implementation must assume the responsibility for the correct semantics of the hashCode, equals, and toString methods inherited from the Object class, so that they behave appropriately for remote objects.

Utilities to Explicitly Export a Remote Object to the RMI System

RemoteObjectExporterInterface defines the behavior required of implementations that provide an explicit export mechanism. The abstract base class AbstractRemoteObjectExporter, which implements RemoteObjectExporterInterface, provides methods to AbstractRemoteObjectExporter.exportObject() and AbstractRemoteObjectExporter.unexportObject() Java remote objects.

The following concrete implementations extend this abstract implementation:


***  This package contains classes that provide Binary Compatibility only, not Source Compatibility  ***

Note:
Extension of the classes in this package is prohibited unless otherwise documented. Similarly, extension or implementation of the interfaces in this package is prohibited except as documented.


Copyright © 2009 SAS Institute Inc. All Rights Reserved.