Connected Device Configuration
| Company type | Specification |
|---|---|
| Industry | Software, Embedded systems |
| Founder | Java Community Process |
| Products | Java ME application framework specification |
The Connected Device Configuration (CDC) represents a Java ME application framework specification that outlines the core libraries and virtual machine capabilities essential for its implementation. When combined with one or more profiles, CDC establishes a development platform suited for embedded devices ranging from pagers to set-top boxes. This specification was created through the Java Community Process as JSR 36 (CDC 1.0.2) and JSR 218 (CDC 1.1.2).
Typical requirements
Devices compatible with CDC generally incorporate a 32-bit CPU, around 2 MB of RAM, and approximately 2.5 MB of ROM allocated for the Java runtime environment. Reference implementations typically run on Linux operating systems hosted on Intel-compatible personal computers, with optimized versions available for various CPU architectures and OS platforms.
Profiles
Within the CDC framework, profiles refer to sets of APIs designed to accommodate devices with differing capabilities, thereby enabling a comprehensive Java application environment. There are three progressively built profiles, allowing developers to choose the model best aligned with their hardware.
Foundation Profile
The Foundation Profile serves as the most fundamental CDC profile, delivering Java APIs tailored for devices with minimal resource footprints and lacking graphical user interfaces. It provides a complete Java ME environment suitable for consumer electronics and embedded systems but does not include a standardized GUI architecture. Version 1.1.2, defined in JSR 219, implements a portion of Java SE 1.4.2 and supports optional security packages such as Java Authentication and Authorization Service (JAAS), Java Secure Socket Extension (JSSE), and Java Cryptography Extension (JCE).
Personal Basis Profile
Building upon the Foundation Profile, the Personal Basis Profile targets devices equipped with lightweight graphical user interfaces. It offers a framework supporting basic GUI components with limited implementation of some AWT classes while excluding heavyweight components that depend on pointing devices like mice. Specified in JSR 217, this profile is appropriate for products requiring standardized GUIs without full AWT compatibility. It utilizes the Xlet programming model, including advanced content delivery on Blu-ray discs adhering to the BD-J specification.
Personal Profile
The Personal Profile enhances the Personal Basis Profile by incorporating a comprehensive AWT-based GUI toolkit.[1] This profile delivers a full-featured Java ME environment with complete AWT support, targeting higher-end embedded devices such as PDAs, smart communicators, set-top boxes, gaming consoles, and automotive dashboards. It is recommended for migrating legacy PersonalJava applications and is defined in JSR 62, employing the Applet programming model.
Optional Packages
To augment functionality within the constraints of Java ME, CDC includes optional packages such as:
- The RMI Optional Package, which provides a subset of Java SE RMI capabilities for distributed applications and network communication.
- The JDBC Optional Package, offering a subset of JDBC 3.0 APIs to facilitate access to various data sources including spreadsheets, flat files, and relational databases.
See also
- Connected Limited Device Configuration (CLDC), an alternative platform for creating Java ME applications
External links
- ↑ Personal Profile Overview