Slide 3.3: J2ME (cont.)

Slide 3.2: J2ME (cont.)
Slide 3.4: Migrating wireless applications to MIDP 2.0, WMA, and MMA
Home

J2ME (Cont.)

Profiles
To provide a complete runtime environment for a specific device category a configuration must be combined with a profile, a set of higher-level APIs that further define the application life-cycle model, the user interface, and access to device-specific properties. A profile supports a narrower category of devices within the framework of a chosen configuration.

There are two standard CLDC-based profiles: Mobile Information Device Profile (MIDP, versions 1.0 and 2.0) and Information Module Profile (IMP).

Three profiles are based on CDC: Foundation Profile (FP), Personal Basis Profile (PBP), and Personal Profile (PP).

Optional Packages
The J2ME platform can be extended by adding various optional packages to a technology stack that includes either CLDC or CDC and an associated profile. Created to address very specific application requirements, optional packages offer standard APIs for using both existing and emerging technologies such as database connectivity, wireless messaging, multimedia, Bluetooth, and Web services. Because optional packages are modular, developers can avoid carrying the overhead of unnecessary functionality by including only the packages an application actually needs.