Java Reference
In-Depth Information
•
CLDC 1.1 and MIDP 2.1
: Provide the foundation platform as specified in JSR 139
and JSR 118.
•
FCOP and PIM
: Provide access to the native file system and personal information
manager. The FCOP must provide properties giving the default URL of the storage
directory for camera-captured photos and videos, wallpaper images, ring tones, music,
and voice recorders, and a private storage directory for each MIDlet. PIM must include
support for the
PIMList
subclasses
ContactList
,
ToDoList
, and
EventList
in read-only,
read-write, and write-only modes.
ContactList
must support fax, home, mobile,
preferred, and work numbers, as well as street-address, e-mail, note, URL, and photo
fields.
ToDoList
must include the summary, priority, completion date, due, and com-
pleted fields. As with other portions of MSA Subset 1.0, these apply to MSA 1.0 as well.
•
Bluetooth
: If the device supports Bluetooth technology, it must include the
Bluetooth API based on the GCF that JSR 82 describes. With this, applications
can exchange media between devices using Bluetooth.
•
MMAPI
: The MMAPI must be included to permit developers to create compelling
multimedia applications. Implementations must support the same resolutions for
image capture from the image sensor as the system camera application.
•
Mobile 3D graphics
: Mobile 3D graphics are an important element for games, some
rich GUIs, and other graphics-intensive applications. A compliant device must
provide the interface that JSR 184 specifies.
•
WMA
: A compliant device must provide WMA 2.0, as messaging is a key phone
feature that must be available to Java ME developers (see Chapter 14).
•
SVG
: Graphics remain a key component of today's and tomorrow's mobile
applications; including support for JSR 226 ensures that applications can
display SVG images.
Examining MSA 1.0
MSA 1.0 builds on MSA Subset 1.0 by adding the following packages:
•
J2ME Web services
: The J2ME Web Services Specification that JSR 172 describes—
both the XML parser and the web services optional package—must be included to
facilitate a standard way to support web services (see Chapter 13).
•
Security and trust services
: SATSA is an important element in a wide variety of
mobile applications and services. SATSA-CRYPTO must be provided, while support
for the APDU interface within SATSA and SATSA-PKI are conditionally mandatory
(see Chapter 15).
