discuss, there is still some way to go until the industry standards leapfrog
to a more powerful CDC configuration (or possibly a mobile platform sim-
ilar to Java SE), and so CDC is not in the scope of the chapter. We discuss
only MSA implemented over the CLDC 1.1 Configuration. For more infor-
mation on MSA and CDC, refer to the Runtime-Execution-Environment
descriptor attribute definition in MIDP 2.1 specification.
We now take a closer look at the Component JSRs in both the full MSA
and MSA Subset platforms. We also give a few examples of Component
JSR requirements that were clarified or added. Figure 6.1 shows MSA and
Figure 6.1 JSR-248 MSA Component JSRs: a) full set and b) subset
An MSA-compliant platform may include a newer version of a Com-
ponent JSR, as long as the newer version is backward-compatible with
the version specified in JSR-248 (however, application developers are
encouraged to develop to the specific versions of the Component JSRs
defined in JSR-248).
For each supported JSR, an MSA-compliant platform should comply
with all the additional requirements for that JSR that are specified by the
MSA. A JSR can be mandatory or conditionally mandatory (see Table 6.1).
An MSA-compliant platform must support all mandatory Component JSRs
that are part of the full MSA or MSA Subset. MSA provides clarifications
that describe the conditions under which the conditionally mandatory
Component JSRs and their optional packages are to be supported. For
example, JSR-179 Location must be supported if the target device has
a GPS receiver that is able to deliver geographical coordinates to other