Introduction - Beginning J2ME: From Novice to Professional - page 10

MIDP 2.0 addresses a long list of the shortcomings inherent with MIDP 1.0. Its timing is
good, so the current adoption and deployment of MIDP 2.0 devices should provide a standard,
unified platform for wireless development.
Another fragmentation issue is the confusion surrounding the assembly of configurations,
profiles, and optional APIs into a software stack. As a developer, you want to understand exactly
what set of APIs will be available or are likely to be available, but there seem to be so many
choices and so many possibilities. The standardization on a software stack, via JTWI (JSR 185—
http://jcp.org/jsr/detail/185.jsp ), should bring clarity to this issue.
Summary
J2ME is the Java platform for small devices, a broad field that covers pretty much everything
smaller than a breadbox. Because J2ME spans such a diverse selection of hardware, it is divided
into configurations, profiles, and optional APIs. A configuration specifies a subset of J2SE func-
tionality and the behavior of the JVM, while profiles are generally more specific to a family of
devices with similar characteristics. Optional APIs offer added functionality in a flexible package.
The Mobile Information Device Profile, which is the focus of this topic, includes APIs for devices
like mobile phones and two-way pagers.