Java Reference
In-Depth Information
run-time environments using another method, such as an accessory
location device.
Table 6.1
MSA 1.1 Component JSRs
JSR
Name
Optionality
JSR-139
CLDC 1.1
Mandatory in MSA and MSA
Subset
JSR-118
Mobile Information Device Profile 2.1
Mandatory in MSA and MSA
Subset
JSR-75
PDA Optional Packages 1.0
Mandatory in MSA and MSA
Subset
JSR-82
Java APIs for Bluetooth 1.1
Conditionally mandatory in MSA
and MSA Subset
JSR-135
Mobile Media API 1.2
Mandatory in MSA and MSA
Subset
JSR-172
J2ME Web Services Specification 1.0
XML parsing is mandatory in
MSA
JSR-177
Security and Trust Services API 1.0:
•
CRYPTO
Mandatory in MSA
•
APDU
Conditionally mandatory in MSA
•
PKI
Conditionally mandatory in MSA
•
JCRMI
Not part of MSA or MSA Subset
JSR-179
Location API for J2ME 1.0.1
Conditionally mandatory in MSA
JSR-180
SIP API for J2ME 1.1.0
Mandatory in MSA
JSR-184
Mobile 3D Graphics API for J2ME 1.1
Mandatory in MSA and MSA
Subset
JSR-205
Wireless Messaging API 2.0
Mandatory in MSA and MSA
Subset
JSR-211
Content Handler API 1.0
Mandatory in MSA
JSR-226
Scalable 2D Vector Graphics API 1.1
Mandatory in MSA and MSA
Subset
JSR-234
Advanced Multimedia Supplements 1.1
Mandatory in MSA
JSR-238
Mobile Internationalization API 1.0
Mandatory in MSA
MSA provides developers with a wider synergy of APIs, predictability
of APIs on devices, ease of development and porting, and less testability.
The advantage of MSA for device manufacturers is that more applications
