While MSA 2.0 will increase the technology support, JSR-271 MIDP
3.0 will bring great advancements to the environment in which Java
applications run. The specification defines:
Shared Java libraries (LIBlets)
Receiving more system events using the javax.microedition.
Inter-MIDlet Communication (IMC)
CLDC 1.1 and CDC 1.1 support
Idle screen MIDlets
Packaging, deployment, installation, and security.
MIDP 3.0 also refers to other ongoing JSRs (e.g. JSR-258 Mobile User
Interface Customization and JSR-307 Network Mobility and Mobile Data
The world of Java applications in a few years from now will be
powerful and different. Imagine a scenario in which two concurrently
running Java applications (MIDlets, or possibly another model, e.g. Xlets)
are both using a shared LBS LIBlet and communicate with each other
using IMC. They will be using advanced features such as JSR-256 Sensor
API, JSR-293 Location API 2.0 and will be able to respond to many more
system events. When they exit, the idle screen MIDlet will start running.
This is definitely something to wait for!
6.5 MSA and Symbian OS
At the time of writing this topic, the first S60 5th Edition smartphones
have been announced and S60 3rd Edition FP2 devices are already in the
Two of the major goals of JSR-248 MSA are alignment to higher
standards and defragmentation. Symbian's strategy has always been to
enable a powerful Java ME run-time environment as required. That means
that there is ongoing progress and new JSRs are added in each Symbian
OS release, either by Symbian or by Symbian OS licensees. The set of
APIs that we detected in Chapter 3 already exceeds the list of Component
JSRs in MSA Subset. As a matter of fact, the detected devices are closer to
full MSA than to MSA Subset.
So you can safely assume that generally the direction of Java ME on
Symbian OS is towards full MSA and beyond. More than that, Java ME on