 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 218: Connected Device Configuration (CDC) 1.1
JCP version in use: 2.6 Java Specification Participation Agreement version in use: 2.0 Description: This JSR defines a revision to the J2ME CDC specification. This JSR provides updates (based on J2SE, v1.4) to the existing core, non-graphical Java APIs for small electronic devices. Please direct comments on this JSR to the Spec Lead(s) Team
The following information has been updated from the original proposal. 2008.09.19: Maintenance Lead: Roger Riggs, Sun Microsystems, Inc. E-Mail Address:
roger.riggs Telephone Number: +1 781 442 0539 Fax Number: +1 781 442 1610
2005.11.09: E-Mail Address:jonathan.courtney Telephone Number: +1 408 276 7398 Fax Number: +1 972 235 5727
2005.05.23: Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification Submitting Member: Sun Microsystems, Inc Name of Contact Person: Hinkmond Wong E-Mail Address: hinkmond.wong@sun.com Telephone Number: +1 408 276 7618 Fax Number: Specification Lead: Hinkmond Wong E-Mail Address:hinkmond.wong@sun.com Telephone Number: +1 408 276 7618 Fax Number: Initial Expert Group Membership: SavaJe Supporting this JSR:
Section 2: Request
2.1 Please describe the proposed Specification:The J2ME CDC is a Configuration of the Java 2 Platform, Micro Edition suitable for types of devices that will supply a network-enabled Java environment. It provides a basis for J2ME Profiles that build upon the CDC by adding a graphical user interface or other functionality. The J2ME CDC targets small, resource-constrained devices (such as high-end PDAs, cell phones, TV set-top boxes, auto telematics, and so on) by supporting the following features:
* Java language * Networking * I/O * Java 2 Security * Text input and display This new JSR will:
* Update APIs already present in the J2ME CDC 1.0, at the discretion of the expert group, to the definitions in J2ME CLDC 1.1. * Add carefully selected additional features or APIs, at the discretion of the expert group, taken from J2SE, v1.4. Note that while new APIs may be adopted from J2SE, v1.4, no new, non-J2SE APIs are planned for definition in this JSR. J2ME CDC 1.1 will be backward compatible with J2ME CDC 1.0. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)Java 2 Platform, Micro Edition (J2ME) Connected Device Configuration 2.3 What need of the Java community will be addressed by the proposed specification?Provides a standard Java 2 Micro Edition Configuration to be used as the basis for profiles that will add GUI as well as other functionality.
* 512KB minimum RAM available * * Robust connectivity to some type of network. * No graphical user interface, unless the GUI functionality is provided by an additional profile. (* Application and localization memory requirements are additional.) 2.4 Why isn't this need met by existing specifications?Updates to APIs already present in CDC 1.0, to match their specifications in J2SE, v1.4 are needed to support J2ME Foundation Profile 1.1, Personal Basis Profile 1.1 and Personal Profile 1.1. Also, J2ME CDC 1.0 does not currently include certain J2SE, v1.4 features that are required by device manufacturers and application developers. Such features, to be incorporated at the discretion of the CDC 1.1 expert group, might include support for the J2SE assertion facility. Assertions are a powerful facility for improving program robustness and must be supported in order to support the current version of the Java programming language. Lastly, at the discretion of the expert group, the J2ME CDC 1.0 APIs that are derived from CLDC 1.0, might be updated to the specifications for those APIs in CLDC 1.1. 2.5 Please give a short description of the underlying technology or technologies:See section 2.1 for expected underlying device technologies. CDC provides core non-graphics Java libraries for support of the underlying Java virtual machine (VM). 2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)The package names for CDC include:
java.lang 2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?No 2.8 Are there any security issues that cannot be addressed by the current security model?None identified at this time. 2.9 Are there any internationalization or localization issues?Requirements to be decided upon by the expert group developing this specification. 2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?The specification for J2ME CDC version 1.0 will be superseded by this specification. 2.11 Please describe the anticipated schedule for the development of this specification.Community Review Draft: June 2003 2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.Consensus-driven, mainly via e-mail, with a private Web site for archiving discussion. We will also be supporting the underlying technology into the JSRs for J2ME Foundation Profile 1.1, Personal Basis Profile 1.1 and Personal Profile 1.1. Because of the tight relationship J2ME CDC 1.1 specification has with J2ME Foundation Profile 1.1 specification, we will create a joint expert group for both of these JSRs and will hold joint meetings, We will do this to ensure that the two JSRs stay tightly synchronized. The expert group will also remain in close communication and cooperation with the Personal Basis Profile 1.1 and Personal Profile 1.1 expert groups. 2.13 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.The RI and TCK will be delivered as part of this configuration work. 2.14 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).
2.15 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.The TCK and RI will be available for license separately:
* TCK:
o Per unit royalty fee which will be dependent on volume. * RI:
o Per unit royalty fee which will be dependent on volume. 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.The J2ME Foundation Profile relies on the J2ME Connected Device Configuration (CDC) as its base configuration. J2ME Foundation Profile 1.1 relies on a minimum of J2ME CDC 1.1 specification to be present..
http://www.jcp.org/en/jsr/detail?id=46 Foundation Profile, version 1.0 (JSR-46) The Java Language Specification, Second Edition, James Gosling, Bill Joy, Guy L. Steele, and Gilad Bracha. Addison-Wesley, 2000, ISBN 0-201-31008-2 The Java Virtual Machine Specification, Second Edition, Tim Lindholm and Frank Yellin. Addison-Wesley, 1999, ISBN 0-201-43294-3 3.2 Explanation of how these items might be used as a starting point for the work.Please see section 2.5. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
