Use is subject to License Terms. Your use of this web site or any of its content or software indicates your agreement to be bound by these License Terms.

Copyright © 2006 Sun Microsystems, Inc. All rights reserved.

CDC 1.1.2

Connected Device Configuration (CDC), version 1.1.2

Connected Device Configuration, version 1.1.2

See:
          Description

Packages
java.io Provides for system input and output through data streams, serialization and the file system.
java.lang Provides classes that are fundamental to the design of the Java programming language.
java.lang.ref Provides reference-object classes, which support a limited degree of interaction with the garbage collector.
java.lang.reflect Provides classes and interfaces for obtaining reflective information about classes and objects.
java.math Provides classes for performing arbitrary-precision integer arithmetic (BigInteger) and arbitrary-precision decimal arithmetic (BigDecimal).
java.net Provides the classes for implementing networking applications.
java.security Provides the classes and interfaces for the security framework.
java.security.cert Provides classes and interfaces for parsing and managing certificates, certificate revocation lists (CRLs), and certification paths.
java.text Provides classes and interfaces for handling text, dates, numbers, and messages in a manner independent of natural languages.
java.util Contains the collections framework, legacy collection classes, event model, date and time facilities, internationalization, and miscellaneous utility classes (a string tokenizer, a random-number generator, and a bit array).
java.util.jar Provides classes for reading and writing the JAR (Java ARchive) file format, which is based on the standard ZIP file format with an optional manifest file.
java.util.zip Provides classes for reading and writing the standard ZIP and GZIP file formats.
javax.microedition.io Provides a simplified mechanism for applications to use various types of I/O protocols in resource-constrained environments.

 

Connected Device Configuration, version 1.1.2

Introduction

The Connected Device Configuration is a Java Platform, Micro Edition (Java ME) 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 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 CDC provides to the Java ME 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.

List of New Features

List of Changes Since Last Release

For a list of changes since the last specification release please use a tool like jdiff to generate differences between specifications.

Adherence to the Java Language Specification

An implementation of 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-31008-2.

Adherence to the Java Virtual Machine Specification

An implementation of 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/2nd-edition/html/VMSpecTOC.doc.html. The specification is also published in book form by Addison-Wesley, ISBN 0-201-43294-3.

Additional Virtual Machine Requirements

If an interface for invoking native methods is included in the CDC implementation, that interface must be the Java Native Interface version 1.1, as well as the JNI enhancements included in Java technology. The Java Native Interface 1.1 specification and the Java enhancements can be found at http://java.sun.com/products/jdk/1.4.2/docs/guide/jni/index.html.

If a debugging interface is included in the 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.4.2/docs/guide/jpda/jvmdi-spec.html.

If a profiling interface is included in the 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.4.2/docs/guide/jvmpi/index.html

Relationship to the J2SE 1.4.2 API Specification

The CDC 1.1.2 API is is based primarily on the J2SE 1.4.2 API. The APIs in this specification must follow the strict conformance of the "Configurations and Profiles Architecture Specification".

Relationship to the CLDC Specification

The CDC 1.1.2 API includes all Java language APIs defined in the CLDC 1.1 specification. This includes both java.* packages defined by CLDC, as well as the javax.microedition package defined in CLDC. In many instances, APIs that were removed from the J2SE API by the CLDC specification are included in the CDC specifcation. The complete CLDC 1.1 specification can be found at http://java.sun.com/aboutJava/communityprocess/final/jsr139/index.html.

Definition of Process Model Support

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.

Security Support

The following security features are NOT supported:

Protocol Support

See: javax.microedition.io package overview: Protocol Support section.

Generic Connection Framework (GCF) Security Checks

See: javax.microedition.io package overview: Generic Connection Framework (GCF) Security Checks section.

Character Encodings

The required character encodings are listed in the overview for:

Networking Support

A conformant implementation need only support loopback communication to the local host. IP network communication to external hosts is not required. If an implementation does not support IP network communication to external hosts, the system property java.net.isRestricted must be set to true. If java.net.isRestricted is set to true, then the APIs of the java.net and java.microedition.io packages shall throw exceptions as specified (i.e., java.io.IOException and subclasses) at any point that external communication would be required, e.g., resolving a host name or establishing a connection.


CDC 1.1.2

Copyright © 2006 Sun Microsystems, Inc. All rights reserved. Use is subject to License Terms. Your use of this web site or any of its content or software indicates your agreement to be bound by these License Terms.

For more information, please consult the JSR 218 specification.