Java Reference
In-Depth Information
Internationalization
AMMS
Bluetooth
WMA
Web Services
Location
SATSA
SVG
MMAPI
MIDP/CLDC
Figure 6.6
MobileAerith enhanced with MSA capabilities
picture scaling and processing was done using advanced features of JSR-
234 AMMS that are not in JSR-135 MMAPI. Figure 6.6 shows the new
version of MobileAerith after the big facelift, using MSA Component JSRs.
MSA's synergy of APIs has enabled us to give added value to an existing
mobile application, whilst at the same time ensuring that it runs on many
more MSA-compliant devices with less version management overhead
6.4 Beyond MSA 1.1: MIDP 3.0 and MSA 2.0
So far we have discussed what MSA 1.1 is and shown some examples
of Java applications that use MSA 1.1. There is even more to expect in
the future. The MSA standardization efforts are intended to be ongoing
activities to define the evolving Java platforms to meet the latest market
requirements.
Apart from JSRs that handle specific technologies and are currently
being worked on, we can already look ahead to JSR-249 MSA 2.0 and
JSR-271 MIDP 3.0, which are being drafted at the time of writing this
topic.
Their release is determined by the time required for mass-market
deployment and the readiness of the relevant Java standards which
themselves depend on technology standardization in other relevant stan-
dardization organizations. Any future standard will strive to maintain
backward compatibility as much as possible and plan ahead to be
forward compatible with future standards.
