Content deleted Content added
m Reverted edits by 2600:100A:B028:F92E:1DEB:D644:6278:AD26 (talk) to last version by Uzume |
BrainStack (talk | contribs) Link suggestions feature: 3 links added. |
||
(34 intermediate revisions by 23 users not shown) | |||
Line 1:
{{Short description|Java application-programming interface}}
[[File:RMI-Stubs-Skeletons.svg|thumb|right|400px|A typical implementation model of Java-RMI using [[Class stub|stub]] and [[Distributed object communication#Skeleton|skeleton]] objects. Java 2 SDK, Standard Edition, v1.2 removed the need for a skeleton.]]
The original implementation depends on [[Java Virtual Machine]] (JVM) class-representation mechanisms and it thus only supports making calls from one JVM to another. The protocol underlying this Java-only implementation is known as
Usage of the term '''RMI''' may denote solely the programming interface or may signify both the API and
The basic idea of Java RMI, the distributed garbage-collection (DGC) protocol, and much of the architecture underlying the original Sun implementation, come from the "network objects" feature of [[Modula-3]].
==Generalized code==
The programmers of the original RMI API generalized the code somewhat to support different implementations, such as a [[
RMI functionality comes in the package {{Javadoc:SE|package=java.rmi|java/rmi|module=java.rmi}}, while most of Sun's implementation is located in the <code>sun.rmi</code> package. Note that with Java versions before Java 5.0, developers had to compile RMI stubs in a separate compilation step using <code>'''rmic'''</code>. Version 5.0 of Java and beyond no longer require this step - and static stubs have been deprecated since Java 8.
==Jini version==
[[Jini]] offers a more advanced version of RMI in Java. It functions similarly but provides more advanced security, object discovery capabilities, and other mechanisms for [[distributed object]] applications.<ref name="From P2P to Web Services and Grids 2005">{{cite book |first=Ian J |last=Taylor |title=From P2P to Web Services and Grids : Peers in a Client/Server World |series=Computer Communications and Networks |publisher=Springer-Verlag |
==Example==
The following classes implement a simple client-server program using RMI that displays a message.
; <code>RmiServerIntf</code> interface : defines the interface that is used by the client and implemented by the server. This extends the {{Javadoc:SE|module=java.rmi|package=java.rmi|java/rmi|Remote}} interface, which serves to identify an implementing class as one with remotely-invokable methods.
'''<code>RmiServer</code> class''' — listens to RMI requests and implements the interface which is used by the client to invoke remote methods.▼
<syntaxhighlight lang=java>▼
import java.rmi.Remote;▼
import java.rmi.RemoteException;▼
public interface RmiServerIntf extends Remote {▼
String getMessage() throws RemoteException;▼
}▼
</syntaxhighlight>▼
▲
<syntaxhighlight lang=java>
Line 39 ⟶ 51:
}
public static void main(String
System.out.println("RMI server started");
Line 60 ⟶ 72:
</syntaxhighlight>
▲<syntaxhighlight lang=java>
▲import java.rmi.Remote;
▲import java.rmi.RemoteException;
▲public interface RmiServerIntf extends Remote {
▲ String getMessage() throws RemoteException;
▲}
▲</syntaxhighlight>
▲'''<code>RmiClient</code> class''' — this is the client which gets the reference (a proxy) to the remote object living on the server and invokes its method to get a message. If the server object implemented java.io.Serializable instead of java.rmi.Remote, it would be serialized and passed to the client as a value.<ref>{{cite web |last1=Wilson |first1=M. Jeff |date=2000-11-10 |df=mdy |url=https://www.infoworld.com/article/2076234/get-smart-with-proxies-and-rmi.html |title=Get smart with proxies and RMI |work=[[JavaWorld]] |accessdate=2020-07-18}}</ref>
<syntaxhighlight lang=java>
Line 77 ⟶ 78:
public class RmiClient {
public static void main(String
RmiServerIntf server = (RmiServerIntf)Naming.lookup("//localhost/RmiServer");
System.out.println(server.getMessage());
Line 86 ⟶ 87:
Before running this example, we need to make a 'stub' file for the interface we used. For this task we have the RMI compiler - 'rmic'
*Note: we make a stub file from the '*.class' file with the implementation of the remote interface, not from the '*.java' file.
rmic RmiServer
Note that since version 5.0 of J2SE, support for dynamically generated stub files has been added, and rmic is only provided for backwards compatibility with earlier runtimes,<ref>{{cite web|title=Java RMI Release Notes|url=http://docs.oracle.com/javase/1.5.0/docs/guide/rmi/relnotes.html|publisher=Oracle|
==References==
Line 95 ⟶ 96:
==External links==
*{{cite web |title=Remote Method Invocation Home |url=http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136424.html |website= Oracle Technology Network for Java Developers |publisher=[[Oracle Corporation]] |___location=Redwood Shores, CA, USA |
* [
*
* [
* {{Javadoc:SE|package=java.rmi|module=java.rmi|java/rmi}} (
* {{cite
| title= A Distributed Object Model for the Java System
| url=http://pdos.csail.mit.edu/6.824/papers/waldo-rmi.pdf |archive-url=https://ghostarchive.org/archive/20221010/http://pdos.csail.mit.edu/6.824/papers/waldo-rmi.pdf
* [http://docs.oracle.com/cd/E12840_01/wls/docs103/rmi/rmi_intro.html Programming WebLogic RMI] - an introduction to RMI in Oracle Weblogic.
* [http://notes.corewebprogramming.com/student/RMI.pdf General Remote Method Invocation]
[[Category:
[[Category:Remote procedure call]]
[[Category:Articles with example Java code]]
|