Download CDC Build System Guide

1.4
Java ME Standard API Choices
The standard API choices available in Java ME technology are based on
configurations, profiles and optional packages described in TABLE 1-1. To construct a
conforming CDC Java runtime environment, a product designer chooses a
configuration, a profile and any number of optional packages.
TABLE 1-1
Standard Java ME API Features
Configuration
Profile
Optional Package
CDC
Foundation
Personal Basis
Personal
RMI
JDBC
Security
For example, a product designer could choose the Connected Device Configuration
(CDC), the Personal Profile and the RMI and JDBC optional packages. See
Section 4.1.3, “Standard API Choices: Profiles and Optional Packages” on page 4-2
for information about how to use build options to select standard API features. See
Section 4.3, “Building a Development Version of the CDC Java Class Library” on
page 4-6 for information about how to build a target development version of the
CDC Java class library.
1.5
Application Development
The CDC application developer compiles Java source code against a CDC Java class
library and then runs the compiled application with a CDC Java runtime
environment for testing and debugging. The companion document CDC Runtime
Guide describes how to compile, run, debug and profile Java applications for the
CDC platform using conventional Java SE tools and the CDC Java runtime
environment.
In general, CDC application development is separate from runtime development.
But there is one scenario where they cross paths. The CDC build system can be used
as part of an application development workflow to bundle Java applications directly
into a CDC Java runtime environment for the purposes of both performance and
convenience. This capability is based on the preloading mechanism described in
Section 4.4, “Preloading Java Class Files with JavaCodeCompact” on page 4-7.
Chapter 1
Introduction
1-3