📄 overview-summary.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN""http://www.w3.org/TR/REC-html40/frameset.dtd"><!--NewPage--><HTML><HEAD><!-- Generated by javadoc on Thu May 30 13:46:48 EDT 2002 --><TITLE>J2ME RMI Optional Package Specification v1.0: Overview</TITLE><LINK REL ="stylesheet" TYPE="text/css" HREF="stylesheet.css" TITLE="Style"></HEAD><BODY BGCOLOR="white"><!-- ========== START OF NAVBAR ========== --><A NAME="navbar_top"><!-- --></A><TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0"><TR><TD COLSPAN=2 BGCOLOR="#EEEEFF" CLASS="NavBarCell1"><A NAME="navbar_top_firstrow"><!-- --></A><TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3"> <TR ALIGN="center" VALIGN="top"> <TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> <FONT CLASS="NavBarFont1Rev"><B>Overview</B></FONT> </TD> <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <FONT CLASS="NavBarFont1">Package</FONT> </TD> <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <FONT CLASS="NavBarFont1">Class</FONT> </TD> <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="overview-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A> </TD> <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A> </TD> <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="index-files/index-1.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A> </TD> <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A> </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"> PREV NEXT</FONT></TD><TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2"> <A HREF="index.html" TARGET="_top"><B>FRAMES</B></A> <A HREF="overview-summary.html" TARGET="_top"><B>NO FRAMES</B></A></FONT></TD></TR></TABLE><!-- =========== END OF NAVBAR =========== --><HR><CENTER><H2>J2ME RMI Optional Package Specification v1.0</H2></CENTER>Java(TM) 2 Platform, Micro Edition, Remote Method InvocationOptional Package Specification v1.0<P><B>See: </B><BR> <A HREF="#overview_description"><B>Description</B></A><P><TABLE BORDER="1" CELLPADDING="3" CELLSPACING="0" WIDTH="100%"><TR BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><TD COLSPAN=2><FONT SIZE="+2"><B>Packages</B></FONT></TD></TR><TR BGCOLOR="white" CLASS="TableRowColor"><TD WIDTH="20%"><B><A HREF="java/rmi/package-summary.html">java.rmi</A></B></TD><TD>Provides the RMI package.</TD></TR><TR BGCOLOR="white" CLASS="TableRowColor"><TD WIDTH="20%"><B><A HREF="java/rmi/activation/package-summary.html">java.rmi.activation</A></B></TD><TD>Provides support for RMI Object Activation.</TD></TR><TR BGCOLOR="white" CLASS="TableRowColor"><TD WIDTH="20%"><B><A HREF="java/rmi/dgc/package-summary.html">java.rmi.dgc</A></B></TD><TD>Provides classes and interface for RMI distributedgarbage-collection (DGC).</TD></TR><TR BGCOLOR="white" CLASS="TableRowColor"><TD WIDTH="20%"><B><A HREF="java/rmi/registry/package-summary.html">java.rmi.registry</A></B></TD><TD>Provides a class and two interfaces for the RMI registry.</TD></TR><TR BGCOLOR="white" CLASS="TableRowColor"><TD WIDTH="20%"><B><A HREF="java/rmi/server/package-summary.html">java.rmi.server</A></B></TD><TD>Provides classes and interfaces for supporting the unicast server sideof RMI.</TD></TR></TABLE><P> <A NAME="overview_description"><!-- --></A><P><h3>Java(TM) 2 Platform, Micro Edition, Remote Method InvocationOptional Package Specification v1.0</h3><h3>Introduction</h3><p>The Java(TM) 2 Platform, Micro Edition (J2ME(TM)), Remote MethodInvocation (RMI) Optional Package is a J2ME Connected DeviceConfiguration (CDC) Optional Package. The J2ME CDC requires acomplete implementation of the Java virtual machine (JVM)*specification and core Java APIs including <code>java.lang</code>,<code>java.io</code>, <code>java.net</code>, and<code>java.util</code>. Implementations of the RMI Optional Packagecan only function on devices that include support for the J2ME CDC andthe Foundation Profile.<p>This document assumes that the reader is familiar with the ConnectedLimited Device Configuration (CLDC) specification available at<p><a href="http://jcp.org/jsr/detail/30.jsp"><code>http://jcp.org/jsr/detail/30.jsp</code></a>,<p>the CDC specification available at<p><a href="http://jcp.org/jsr/detail/36.jsp"><code>http://jcp.org/jsr/detail/36.jsp</code></a>,<p>the Foundation Profile specification available at<p><a href="http://jcp.org/jsr/detail/46.jsp"><code>http://jcp.org/jsr/detail/46.jsp</code></a>,<p>and the Java 2 Platform, Standard Edition (J2SE(TM)) 1.3 RMIspecification available at<p><a href="http://java.sun.com/j2se/1.3/docs/guide/rmi/spec/rmiTOC.html"><code>http://java.sun.com/j2se/1.3/docs/guide/rmi/spec/rmiTOC.html</code></a>.<p>Note that J2ME Configurations and Profiles are defined in theConnected Limited Device Configuration Specification, Appendix 1, andJ2ME Optional Packages are defined in the J2ME Platform Specificationavailable at<p><a href="http://jcp.org/jsr/detail/68.jsp"><code>http://jcp.org/jsr/detail/68.jsp</code></a>.<p>This document specifies the subset of the J2SE 1.3 RMI API that isincluded in the RMI Optional Package. Information on the J2SE 1.3 RMIAPI is available at<a href="http://java.sun.com/j2se/1.3/docs/api/java/rmi/package-summary.html"><code>http://java.sun.com/j2se/1.3/docs/api/java/rmi/package-summary.html</code></a><p><p>This specification was developed under the Java Community Process(SM).More information on the Java Community Process is available at<a href="http://jcp.org/"><code>http://jcp.org/</code></a>.<h3>Relationship to the J2SE 1.3 API Specification</h3><p>The API for the J2ME RMI Optional Package is a subset ofthe J2SE 1.3 RMI API that may be used with J2ME. Where not explicitlystated, this RMI Optional Package conforms to the J2SE 1.3 RMIspecification. Classes from the J2SE 1.3 RMI API are completelysupported, or modified in ways allowed by the J2MEPlatform Specification. Implementations of the RMI Optional Packagemust support the following "client-oriented" interfaces andfunctionality specified by the J2SE 1.3 RMI API:<ul> <li> <p> Full RMI call semantics <p> The RMI infrastructure supports passing serializable objects as the arguments and return values of remote method invocations. When the code for the class of an object within a remote method invocation's arguments or return value is not available to the JVM that is receiving the object, RMI will use dynamic class loading to obtain the class definition and make it available to the receiving JVM. Implementations of the RMI Optional Package must implement full RMI call semantics, including dynamic class loading. <p><li> Marshalled object support <p>This specification requires support of marshalled object manipulation and persistence through the <code>java.rmi.MarshalledObject</code> API.</ul><ul> <p><li> RMI wire protocol <p> The J2SE 1.3 RMI specification describes a wire protocol that enables remote method invocations to be communicated over a network. Except where noted below, implementations of this optional package must support this wire protocol, known as JRMP. </ul><ul> <p><li> Export of remote objects through the <code>java.rmi.server.UnicastRemoteObject</code> API <p> This specification requires implementations of the RMI Optional Package to support the "export" of unicast remote object implementations. When a remote object implementation is exported to the RMI runtime, remote method invocations from clients of that object will be dispatched to and executed by the implementation object. <p><li> Client and server side distributed garbage collection and garbage collector interfaces <p> An implementation of the RMI Optional Package must include these interfaces and support the RMI distributed garbage collection mechanism, which allows remote implementation objects to be garbage collected when all remote and local references to that object have been discarded. <p><li> The activator interface and the client side activation protocol <p> As of J2SE 1.2, RMI remote object stubs can contain a remote reference to an "activatable" object. Activatable objects can be active or inactive. Remote references to activatable objects engage in an activation protocol that causes an inactive remote object to become active when a remote method is invoked on the object. The remote reference contained in a client stub object is responsible for engaging in the activation protocol. An implementation of the RMI Optional Package must support a remote object reference type that will engage in the activation protocol. <p><li> Registry interfaces and export of a Registry remote object <p> An implementation of the RMI Optional Package must support lookup of remote objects through the standard registry interfaces ⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -