From 554fd8c5195424bdbcabf5de30fdc183aba391bd Mon Sep 17 00:00:00 2001 From: upstream source tree Date: Sun, 15 Mar 2015 20:14:05 -0400 Subject: obtained gcc-4.6.4.tar.bz2 from upstream website; verified gcc-4.6.4.tar.bz2.sig; imported gcc-4.6.4 source tree from verified upstream tarball. downloading a git-generated archive based on the 'upstream' tag should provide you with a source tree that is binary identical to the one extracted from the above tarball. if you have obtained the source via the command 'git clone', however, do note that line-endings of files in your working directory might differ from line-endings of the respective files in the upstream repository. --- libjava/classpath/javax/rmi/package.html | 76 ++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 libjava/classpath/javax/rmi/package.html (limited to 'libjava/classpath/javax/rmi/package.html') diff --git a/libjava/classpath/javax/rmi/package.html b/libjava/classpath/javax/rmi/package.html new file mode 100644 index 000000000..6014c8c85 --- /dev/null +++ b/libjava/classpath/javax/rmi/package.html @@ -0,0 +1,76 @@ + + + + +GNU Classpath - javax.rmi.CORBA + + +

+Java RMI over IIOP combines RMI technology with CORBA technology. Like plain RMI, +RMI over IIOP allows to work completely in the Java programming language +(no IDL). When CORBA needs a separate helper class for each structure being +passed, RMI over IIOP only needs stubs and ties for the objects that are remotely +accessible. As a result, development with RMI-IIOP is easier. However the +specialised pure CORBA helpers needs no reflection to transfer they structures +and hence may be faster than methods, used by both RMI-IIOP and plain RMI. +

+Like RMI, RMI over IIOP provides flexibility by allowing to pass any serializable +Java object (Objects By Value) between application components. A certain +"imaginary IDL" is automatically supposed; this IDL can be explicitly generated +and later used to interoperate with non-java application. +

+Like CORBA, RMI over IIOP is based on open standards defined with the +participation of hundredsof vendors and users in the OMG. It uses IIOP +communication protocol that provides much better interoperability with other +programming languages. +

+With RMI/IIOP you can use advanced CORBA features: multiple objects per servant +and servants per object, servant activators and locators, servant, client and +ior interceptors, CORBA naming service, various ORB policies, stringified object +references and so on. This functionality is based on CORBA value type standard. +RMI/IIOP supports (and GNU Classpath implements) transferring of the arbitrary +connected object graphs (graph flattenning). +

+GNU Classpath RMI-IIOP functionality is implemented as described in +OMG formal/03-09-04 (IDL to Java mapping v1.3). Value types are written as +described in formal/04-03-12 (CORBA 3.0.3). +

+@author Wu Gansha (gansha.wu@intel.com), headers. +@author Audrius Meskauskas (AudriusA@Bioinformatics.org), implementation. + + -- cgit v1.2.3