 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 66: RMI Optional Package Specification Version 1.0
NOTICE: Please be aware the CDC 1.0 specification initially related to this JSR has been replace (superseded) with the newer CDC 1.1 specification. CDC 1.0 will no longer be supported after 18-Aug-2009. This JSR and other optional technologies based on the CDC 1.0 standards are fully compatible with the CDC 1.1 standards. All development and certification efforts should be updated to use the current, supported technology. The following changes have been made to the JSR from the original JSR: Section 1. Identification Submitting Participant: Sun Microsystems, Inc. Name of Maintenance Lead: Mark Hodapp E-Mail Address: Mark.Hodapp@sun.com Telephone Number: +1 781 442 2035 Fax Number: +1 781 442 1657 Original Java Specification Request (JSR) Identification | Request | Contributions Section 1. Identification Submitting Participant: Sun Microsystems, Inc. Name of Contact Person: Mark Hodapp E-Mail Address: Mark.Hodapp@sun.com Telephone Number: +1 978 442 2035 Fax Number: +1 978 442 1657 This information has been updated since the original. Section 2: Request
2.1 Please describe the proposed Specification:The J2ME[tm] RMI Profile provides the Java to Java remote
method invocation environment for those devices. This Profile is intended
to be interoperable with J2SE[tm] RMI and has the explicit requirement of
of providing compatibility with applications developed for versions J2SE
1.2.x or higher (for those J2SE features implemented in the RMI Profile).
The J2ME RMI Profile is targeted for devices characterized with the following capabilities:
* Application and localization memory requirements are additional. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)Java 2 Micro Edition 2.3 What need of the Java community will be addressed by the proposed specification?Provide a standard Java 2 Micro Edition profile for devices with relatively limited resources with the ability to interoperate with RMI on other J2ME or J2SE virtual machines (either devices or services). Part of this demand is coming from partners who wish to deploy Jini[tm] Technology on devices. 2.4 Why isn't this need met by existing specifications?Previous profile JSR have considering including RMI. They have could not justify the memory footprint of including RMI against the current usage. The demand is increasing and many partners believe that RMI should be made available. The only alternative is to deliver the RMI profile. 2.5 Please give a short description of the underlying technology or technologies:See section 2.1. 2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)N/A 2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?See section 2.1. 2.8 Are there any security issues that cannot be addressed by the current security model?None. 2.9 Are there any internationalization or localization issues?None known at this time. 2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?None. Section 3: Contributions
3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.For more information about configurations and profiles, please see the J2ME whitepaper. This whitepaper provides a framework but is not an API proposal. The RMI Profile will be based upon RMI specified in: 3.2 Explanation of how these items might be used as a starting point for the work.The J2ME white paper provides a framework for defining a profile. The J2SE RMI specification will be the basis for the J2ME RMI Profile. |
