Last updated
The Java 2 Platform, Micro Edition, Connected Device Configuration is a J2ME configuration. This configuration is intended to be used by devices requiring a complete implementation of the Java virtual machine, and an API set that may, via the addition of profiles, include the entire Java 2 Platform, Standard Edition API. Typical implementations will use some subset of that API set depending on the profiles supported. This document describes the facilities that the J2ME CDC provides to the J2ME profiles that use it. This specification was developed under the Java Community Process. More information on the Java Community Process is available at http://java.sun.com/jcp.
An implementation of the J2ME-CDC requires full support for the Java programming language as defined in the The Java Language Specification which can be found at http://java.sun.com/docs/books/jls/index.html. The specification is also published in book form by Addison-Wesley, ISBN 0-201-63451-1.
An implementation of the J2ME-CDC requires full support for the Java virtual machine as defined in The Java Virtual Machine Specification which can be found at http://java.sun.com/docs/books/vmspec/index.html. The specification is also published in book form by Addison-Wesley, ISBN 0-201-43294-3.
If an interface for invoking native methods is included in the J2ME-CDC implementation, that interface must be the Java Native Interface version 1.1, as well as the JNI enhancements included in Java 2. The Java Native Interface 1.1 specification and the Java 2 enhancements can be found at http://java.sun.com/products/jdk/1.3/docs/guide/jni/index.html.
If a debugging interface is included in the J2ME-CDC implementation, that interface must be the Java Virtual Machine Debugging Interface. The JVMDI specification can be found at http://java.sun.com/products/jdk/1.3/docs/guide/jpda/jvmdi-spec.html.
If a profiling interface is included in the J2ME-CDC implementation, that interface must be the Java Virtual Machine Profiling Interface. The JVMPI specification can be found at http://java.sun.com/products/jdk/1.3/docs/guide/jvmpi/index.html
The J2ME-CDC API is is based primarily on the J2SE 1.3 API. The APIs in this specification must follow the strict conformance of the "J2ME Configurations and Profiles Architecture Specification".
The J2ME-CDC API includes all Java language APIs defined in the J2ME-CLDC specification. This includes both java.* packages defined by the CLDC, as well as the javax.microedition package defined in the CLDC. In many instances, APIs that were removed from the J2SE API by the CLDC specification are included in the CDC specifcation. The complete J2ME-CLDC specification can be found at http://java.sun.com/aboutJava/communityprocess/final/jsr030/index.html.
Process model support from an underlying operating system is defined by atomic instances of an executing program with a separate existence from all the other atomic instances on the system. Each of these instances has its own address space and can control its own resources. When a process is destroyed or killed, all processes forked from a single Java VM are destroyed and all associated resources (memory, I/O, files, etc.) are cleanly released by the operating system.
The following security features are NOT supported:
The following connection protocols must be supported:
The Generic Connection Framework of J2ME CDC must behave as defined below for the following protocols: 1. File URL as defined by RFC 1738 (http://www.w3.org/Addressing/rfc1738.txt) with the format "file:{path}" must return a object with behavior that follows javax.microedtion.io.InputConnection interface specification with at least support for the "read-only" mode. 2. Datagram Socket as defined by javax.microedition.io.DatagramConnection with the format "datagram://[{host}]:{port}" must return an object with behavior that follows the javax.microedition.io.DatagramConnection interface specification.
The following locale must be supported:
The following encodings must be supported: