MSA Component JSRs

Configuration provides the most basic set of libraries and limited Java Virtual Machine capabilities for Java ME devices.


Kilobytes Virtual Machine (KVM)

Kilobytes Virtual Machine (KVM) is a compact, portable Java Virtual Machine designed for resource-constrained devices. These devices typically contain 16 or 32 bit processors and a minimum memory footprint of approximately 128 kilobytes. KVM maintains all the aspects of the Java programming language, and runs in a resource-constrained device with only a few hundred kilobytes of total memory budget.

Connected Limited Device Configuration (CLDC)
CLDC is designed for mobile devices. This configuration typically has the following features.  


  •160 – 512K of memory available for Java.
  •Typically has limited power or battery operated.
  •Network connectivity, often wireless, intermittent, low-bandwidth.
  •Core Java class libraries available on a particular category of devices.
  •32 kilobytes memory for runtime memory allocation.

Profile

Profile adds domain-specific classes and helps to create interactive applications. The most popular profile is Mobile Information Device Profile (MIDP). Currently MIDP 1.0, MIDP 2.0 & 2.1 are the versions of MIDP. There are number of profiles available such as Foundation Profile, Personal Basis, Personal and RMI profiles each having its specific features and target devices.

Mobile Information Device Profile (MIDP)

MIDP is set of Java APIs and it is more domain specific than the class libraries of CLDC. This addresses the user to persistence storage, networking and user interface where the prime focus is on the guaranteed interoperability within certain devices family. One of the core features of the Mobile Information Device Profile (MIDP) technology is its support for developing user interfaces.

Mobile Information Device has the following specifications:

The primary focus of the MIDP_NG specification scope will address

  •Backward compatibility with MIDP 1.0
  •Continued focus on small, high-volume wireless phones •Maintain tight footprint objectives to limit growth in the core APIs
  •Information learned from MIDP 1.0 deployments to fine tune MIDP 1.0 APIs
  •Focus on core functions needed by all devices and applications
  •Focus on enabling mCommerce, service-based applications