Java remote method invocation: Difference between revisions

Revision as of 12:42, 20 August 2014

Revision as of 23:12, 28 August 2014

Line 88:

</source>

Before running this example, we need to make a 'stub' file offor 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.

<source lang=dos>

Line 95:

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|accessdate=9 May 2012}}</ref> or for programs that don't provide an explicit port number (or zero) when exporting remote objects, which is required for generated stubs to be possible, as described in the Javadoc for UnicastRemoteObject. See the comment in the constructor above.

==Genesis==

The basic idea of Java RMI, the distributed garbage-collection (DGC) protocol, and much of the architecture underying the original Sun implementation, come from the 'network objects' feature of [[Modula-3]].

==References==

{{reflist}}