Package ibis.rmi

This is an RMI implementation on top of Ibis.

See:
Description

Interface Summary

Remote

The Remote interface serves to identify interfaces whose methods may be remotely invoked.

Class Summary

Naming	The Naming class provides static methods for storing and obtaining references to remote objects.
RMISecurityManager	This RMISecurityManager class is here for applications that happen to install one.

Exception Summary

AccessException	The AccessException is never actually thrown in Ibis RMI.
AlreadyBoundException	An AlreadyBoundException is thrown if an attempt is made to bind an object in the registry to a name that is already in use.
ConnectException	A ConnectException is thrown if a connection is refused.
MarshalException	A MarshalException is thrown if an IOException occurs while marshalling the remote call or return value.
NotBoundException	A NotBoundException is thrown if an attempt is made to lookup or unbind a name that has no binding.
RemoteException	A RemoteException is the common superclass for several exceptions that may occur during a remove method invocation.
ServerError	A ServerError is thrown when an Error is thrown while processing a remote method invocation on the server.
ServerException	A ServerException is thrown when a RemoteException is thrown while processing a remote method invocation on the server.
ServerRuntimeException	A ServerRuntimeException is thrown when a RuntimeException is thrown while processing a remote method invocation on the server.
StubNotFoundException	A StubNotFoundException is thrown if no valid stub class could be found while exporting a remote object.
UnknownHostException	An UnknownHostException is thrown when the java.net version of same occurs while creating a connection to a remote host.
UnmarshalException	An UnmarshalException is thrown when an unmarshalling error occurs.

Package ibis.rmi Description

This is an RMI implementation on top of Ibis. This package and its sub-packages implement an (incomplete) version of Java RMI on top of the Ibis communication layer. The most notable difference with "ordinary" Java RMI applications is that an Ibis RMI application must start its own RMI registry. In addition, the Ibis RMI package is called ibis.rmi and not java.rmi. However, the Ibis rmic takes care of that by rewriting the bytecode, so the user can use java.rmi, as long as the Ibis RMI rmic is used.