overview-summary.html

请笑纳 请笑纳 请笑纳 请笑纳 请笑纳 请笑纳

    <code>java.rmi.registry.Registry</code>,
    <code>java.rmi.registry.LocateRegistry</code>,
    and the class <code>java.rmi.Naming</code>
    
    <p><li>
    All system properties defined by the J2SE 1.3 RMI specification
    except those noted in the section below are part of the RMI
    Optional Package specification.

    <p><li> The complete J2ME 1.3 <a href="overview-tree.html">RMI
    Optional Package API</a> is also part of this specification

</ul>
<p>
The following interfaces and functionality defined by the J2SE 1.3 RMI
specification and API are <b><i>not</i></b> part of the specification
for this RMI Optional Package and cannot be added to a conforming RMI
Optional Package implementation:
<ul>
    <p><li>
    RMI Through Firewalls Via HTTP Proxies
    
    <p>The RMI protocol for remote call tunneling over HTTP. This
    protocol enables clients that are separated from remote objects by
    a firewall to &quot;tunnel&quot; remote method invocation through
    the firewall to the remote object implementation through one or
    more HTTP proxies.
    
    <p><li>
    RMI's Multiplexing Protocol
    
    <p>The protocol described in section 10.6 of the J2SE 1.3 RMI
    specification for enabling multiple logical data streams to be
    multiplexed onto a single physical data stream. This protocol can
    enable two JVMs to invoke symmetric remote methods on each other
    even when only a single communication stream exists between the
    two JVMs.
    
    <p><li>
    Implementation Model for an &quot;Activatable&quot; Remote Object 
    
    <p>
    The RMI mechanism for supporting activatable remote object
    implementations enables a remote object to become inactive when it
    is not in use and to become active when a client invokes a method
    on that implementation. Server side support for Activatable
    objects and the Remote Method Invocation Daemon (rmid) are not
    part of this specification.

    <p>
    The following J2SE 1.3 RMI APIs related to the implementation
    model for an "activatable" object are not part of the RMI Optional
    Package API:
    
    <ul>
    <p>
    <i>Interfaces:</i>
    <p>
    <code>
    java.rmi.activation.ActivationInstantiator<br>
    java.rmi.activation.ActivationMonitor<br>
    java.rmi.activation.ActivationSystem<br>
    </code>
        
    <p>
    <i>Classes:</i>
    <p>
    <code>
    java.rmi.activation.Activatable<br>
    java.rmi.activation.ActivationDesc<br>
    java.rmi.activation.ActivationGroup<br>
    java.rmi.activation.ActivationGroupDesc<br>
    java.rmi.activation.ActivationGroupID<br>
    java.rmi.activation.UnknownGroupException<br>
    </code>
    </ul>

    <p>
    See the discussion of system properties below for the missing RMI
    activation property.
    
    <p><li>
    Deprecated methods, classes, and interfaces
    
    <p>The following J2SE 1.3 RMI APIs, which were deprecated as of
    J2SE 1.3, are not part of this specification:

    <ul>
    <p>
    <i>Interfaces:</i>
    <p>
    <code>
    java.rmi.server.ServerRef
    </code>
    
    <p>
    <i>Classes:</i>
    <p>
    <code>
    java.rmi.registry.RegistryHandler<br>
    java.rmi.RMISecurityException<br>
    java.rmi.server.LoaderHandler<br>
    java.rmi.server.LogStream<br>
    java.rmi.server.Skeleton<br>
    java.rmi.server.SkeletonMismatchException<br>
    java.rmi.server.SkeletonNotFoundException<br>
    java.rmi.ServerRuntimeException<br>
    </code>
        
    <p>
    <i>Methods:</i>
    <p>
    <code>
    java.rmi.dgc.VMID.isUnique()<br>    
    java.rmi.server.Operation.getOperation()<br>
    java.rmi.server.RemoteCall.getInputStream()<br>
    java.rmi.server.RemoteCall.getOuputStream<br>
    java.rmi.server.RemoteCall.releaseOuputStream()<br>
    java.rmi.server.RemoteCall.releaseInputStream()<br>
    java.rmi.server.RemoteCall.getResultStream(boolean)<br>
    java.rmi.server.RemoteCall.executeCall()<br>
    java.rmi.server.RemoteCall.done()<br>
    java.rmi.server.RemoteRef.done(RemoteCall)<br>
    java.rmi.server.RemoteRef.invoke(RemoteCall)<br>
    java.rmi.server.RemoteRef.newCall(RemoteObject, Operation[], int, long)<br>
    java.rmi.server.RemoteStub.setRef(RemoteStub, RemoteRef)<br>
    java.rmi.server.RMIClassLoader.getSecurityContext(ClassLoader)<br>
    java.rmi.server.RMIClassLoader.loadClass(String)<br>
    </code>
    </ul>

    <p>The following class in the J2SE 1.3 RMI API is also not part of
    this specification:

    <ul>
    <p>
    <code>
    java.rmi.server.SocketSecurityException
    </code>
    </ul>
    
    <p><li>
    Stub and Skeleton Compiler
    
    <p>
    The J2SE 1.3 specification describes a tool that generates and
    compiles code for RMI stubs and skeletons (known as
    <tt>rmic</tt>).  This RMI Optional Package specification does
    not require such a stub and skeleton compiler
    utility. Applications that need to generate RMI stub classes to be
    used with an implementation of the RMI Optional Package can use
    the stub compiler that is part of the J2SE 1.3 distribution.
    
    <p><li>
    Support for the JDK 1.1 stub/skeleton protocol:
    
    <p>In JDK 1.1, RMI supported a single &quot;stub/skeleton&quot;
    protocol for communication between a client-side stub and the
    server-side skeleton used to carry out the actual invocations on a
    remote object. In J2SE 1.2, RMI added support for an improved stub
    protocol that does not require any application-specific
    server-side skeleton classes. The older, JDK 1.1 stub/skeleton
    protocol is not part of this specification.  The RMI Optional
    Package only supports application stub classes that use the 1.2
    stub protocol. Stubs that are compatible with both the 1.1 and 1.2
    stub protocols (such as those generated using the
    <tt>-vcompat</tt> command line option to the <tt>rmic</tt> stub
    compiler) are supported by the RMI Optional Package, but all RMI
    Optional Package communication must be carried out over the 1.2
    stub protocol except for communication with a distributed garbage
    collector implementation and standard registry implementations.
    
    <p>
    Please see the following URLs for further information on rmic:
    
    <p>
    For the Solaris(TM) Operating Environment: 
    
    <p><a href="http://java.sun.com/j2se/1.3/docs/tooldocs/solaris/rmic.html">
    <code>http://java.sun.com/j2se/1.3/docs/tooldocs/solaris/rmic.html</code></a>
    
    <p>For the Microsoft Windows platform: 
    
    <p><a href="http://java.sun.com/j2se/1.3/docs/tooldocs/win32/rmic.html">
    <code>http://java.sun.com/j2se/1.3/docs/tooldocs/win32/rmic.html</code></a>
</ul>
<ul>
    <p><li>
    The following system properties defined by the J2SE 1.3 RMI
    specification are not part of the RMI Optional Package
    Specification:

    <p>
    <code>
    java.rmi.server.disableHttp<br>
    java.rmi.activation.port<br>
    java.rmi.loader.packagePrefix<br>
    java.rmi.registry.packagePrefix<br>
    java.rmi.server.packagePrefix<br>
    </code>

</ul>
<h3>Relationship to the CLDC Specification</h3>

<p>
The RMI Optional Package requires implementations of the Foundation
Profile and the J2ME CDC. The RMI Optional Package for J2ME/CDC is not
supported by the J2ME Connected Limited Device Configuration (CLDC).

<p>
* As used on this webpage, the terms "Java virtual machine" or "JVM"
mean a virtual machine for the Java platform.
<P>
<HR>

<!-- ========== START OF NAVBAR ========== -->
<A NAME="navbar_bottom"><!-- --></A>
<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0">
<TR>
<TD COLSPAN=2 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
<A NAME="navbar_bottom_firstrow"><!-- --></A>
<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3">
  <TR ALIGN="center" VALIGN="top">
  <TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> &nbsp;<FONT CLASS="NavBarFont1Rev"><B>Overview</B></FONT>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Package</FONT>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Class</FONT>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="overview-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="index-files/index-1.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A>&nbsp;</TD>
  </TR>
</TABLE>
</TD>
<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
J2ME RMI Optional Package</EM>
</TD>
</TR>

<TR>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
&nbsp;PREV&nbsp;
&nbsp;NEXT</FONT></TD>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
  <A HREF="index.html" TARGET="_top"><B>FRAMES</B></A>  &nbsp;
&nbsp;<A HREF="overview-summary.html" TARGET="_top"><B>NO FRAMES</B></A></FONT></TD>
</TR>
</TABLE>
<!-- =========== END OF NAVBAR =========== -->

<HR>
<font size="-1">Copyright 1994-2002 Sun Microsystems, Inc. All Rights Reserved.</font> 
</BODY>
</HTML>