java.rmi.registry Documentation Differences

This file contains all the changes in documentation in the package java.rmi.registry as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

LocateRegistry is used to obtain a reference to a bootstrap remote object registry on a particular host (including the local host) or to create a remote object registry that accepts calls on a specific port.

Note that a getRegistry call does not actually make a connection to the remote host. It simply creates a local reference to the remote registry and will succeed even if no registry is running on the remote host. Therefore a subsequent method invocation to a remote registry returned as a result of this method may fail. @version 1.15 0722 02/1502/9800 @author Ann Wollrath @author Peter Jones @since JDK1.1 @see java.rmi.registry.Registry

Creates and exports a Registry on the local host that uses custom socket factories for communication with that registry. The registry that is created listens for incoming requests on the given port using a ServerSocket created from the supplied RMIServerSocketFactory. A client that receives a reference to this registry will use a Socket created from the supplied RMIClientSocketFactory. @param port port on which the registry accepts requests @param csf client-side Socket factory used to make connections to the registry @param ssf server-side ServerSocket factory used to accept connections to the registry @return the registry @exception RemoteException if the registry could not be exported @since JDK11.2

Returns a locally created remote reference to the remote object Registry on the specified host and port. Communication with this remote registry will use the supplied RMIClientSocketFactory csf to create Socket connections to the registry on the remote host and port. @param host host for the remote registry @param port port on which the registry accepts requests @param csf client-side Socket factory used to make connections to the registry. If csf is null then the default client-side Socket factory will be used in the registry stub. @returnsreturn reference (a stub) to the remote registry @exception RemoteException if the reference could not be created @since JDK11.2

For obtaining references to remote objects RMI provides a simple remote object registry interface implemented by RMI's rmiregistry that provides methods for storing and retrieving remote object references. The java.rmi.Naming class provides methods to access a remote object registry using URL-formatted names to specify in a compact format both the remote registry along with the name for the remote object.

Typically a "registry" exists on every node that allows RMI connections to servers on that node. A registry on a particular node contains a transient database that maps names to remote objects. When a registry starts up the registry database is empty. The names stored in the registry are pure and are not parsed. A service storing itself in the registry may want to prefix its name of the service by a package name (although not required) to reduce name collisions in the registry.

To create a registry that runs in an application use one of the LocateRegistry.createRegistry methods. To obtain a reference to a remote object registry use one of the LocateRegistry.getRegistry methods. @version 1.9 0913 02/2102/9800 @author Ann Wollrath @since JDK1.1 @see java.rmi.Naming @see java.rmi.registry.LocateRegistry

Returns an array of the names bound in the registry. The names are URL-formatted strings. The array contains a snapshot of the names present in the registry at the time of the call. @param name a URL-formatted name that specifies the remote registry @return an array of names (in the appropriate URL format) bound in the registry @exception MalformedURLExceptionRemoteException if the nameregistry iscould not an appropriately formattedbe URLcontacted @exception RemoteExceptionAccessException if registrythis couldoperation is not bepermitted contacted(if originating from a non-local host for example) @since JDK1.1

Well known port for registry.

RegistryHandler is an interface used internally by the RMI runtime in previous implementation versions. It should never be accessed by application code. @version 1.5 0910 02/2102/9800 @author Ann Wollrath @since JDK1.1 @deprecated no replacement

Constructs and exports a Registry on the specified port. The port must be non-zero. @deprecated no replacement. As of JDK1the Java 2 platform v1.2 RMI no longer uses the RegistryHandler to obtain the registry's implementation. @param port port to export registry on @return registry stub @throws RemoteException if a remote error occurs

Returns a "stub" for contacting a remote registry on the specified host and port. @deprecated no replacement. As of JDK1the Java 2 platform v1.2 RMI no longer uses the RegistryHandler to obtain the registry's stub. @param host name of remote registry host @param port remote registry port @return remote registry stub @throws RemoteException if a remote error occurs @throws UnknownHostException if unable to resolve given hostname