Java Programing laungage

J2ME Projects

J2ME Project 1

J2ME profiles
Previous Home Next

Profile play important role in making the J2ME architecture, different kind of Profiles are:

  1. KJava Profile
  2. Java is Sun proprietary profile and contains the Java API and sit on the top of CLDC configuration. It contain a KVM or KJava Virtual Machine similar like J2SE virtual Machine and accepts same byte of codes and class file format. It's specially contain sun- specific API that runs on the Palm OS and deal with the J2SE Abstract Windowing Toolkit (AWT) functionality for testing the CLDC.

    Its main package is com.sun.kjava and GUI classes provide in this package for J2ME will be define separately through the Java Community Process and included in J2ME profiles. This profile (KJava) has been widely used by early and replace by MIDP profile. However, some third-party development tools have implemented commercial versions of KJava Profile (such as esmertec’s Jbed).

  3. Mobile Information Device Profile (MIDP)
  4. MIDP is specification published for the use of Java, mobile devices, and embedded system. It is a part of Java Micro Edition (Java ME) framework and top of a Connected Limited Device Configuration (CLDC). The first MIDP device was launched in April 2001, developed under the Java Community Process.

    Specification of MIDP launch under the Java Community Process.

    • MIDP 1.0 (JSR 37) - Approved on September 19, 2000
    • MIDP 2.0 (JSR 118) - Approved on November 20, 2002
    • MIDP 3.0 (JSR 271) - Approved on December 9, 2009

    Core application programming interfaces (APIs) of MIDP

    • javax.microedition.lcdui
    • javax.microedition.rms
    • javax.microedition.midlet
  5. Personal Digital Assistance Profile (PDAP)
  6. PDAP is specifically designed for Palmtop or similar devices with limited power, typical battery operated, user interface displays like a pointing device and character input, with minimum of 512kb (and maximum 16MB) combined ROM (read only memory) and RAM (random access memory) hardware.

  7. Personal Profile
  8. Personal profile specification repacks the Personal Java APIs Environment to provide J2ME specification for devices that need a high degree of Internet connectivity. This profile builds on top of Foundation profile.

  9. Personal Basic profile
  10. This profile is intended to provide basic Graphical User Interface (GUI) capabilities to devices where the high-fidelity, feature-rich Personal Profile is not fully utilized or necessary means which running the CDC and Foundation Profile.

  11. RIM Profile
  12. RMI profile also builds on top of Foundation profile and supports inter-application RMI over TCP/IP connections for applications written to the Foundation Profile. It's provides the infrastructure to marshal objects as the parameters and return values of remote method calls while the dynamic class loading is utilized to make the marshalled objects available to a particular JVM during a remote call. A special type of protocol - wire protocol JRMP (Java Remote Method Protocol) is required for supported.

    Core Application Programming Interface (APIs) of RMI:

  13. Foundation Profile
  14. The Foundation profiles specified for devices that can support a rich networked J2ME environment. It provides services for other device-specific profiles (such as Personal profile and RMI profile) to be layered on top of it.

    This profile specific design for CDC profiles that provide Graphical User Interface (GUI), Data storage, and distribution of java networking.

  15. Multimedia Profile
  16. This profile target the CLDC and CDC profile to provide basic multimedia support like playing sound, playing video and other media but this profile is not compatible with Java Media Framework (JMF). The core APIs of this profile will provide the controlling time based media such as sound and video along with sampling, streaming and synthetic audio capabilities. The profile is being designed for scalability, providing a set of basic services for more limited devices with a set of optional features for more powerful devices.

  17. Gaming Profile
  18. This profile provide the gaming interface for devices by include 3D model, physical modeling, character animation, rendering, 2D rendering, video buffering, gaming marshalling, network communication, streaming media, sound, game controller support, and hardware access. The CDC is target environment for this profile.

  19. Wireless Telephony Communications API (WTCA)
  20. This profile addressing the J2ME application with a reusability set of components support Short Messages Service (SMS) for receiving and sending message, Unstructured Supplementary Services Data (USSD) for exchange data, and Cell Broadcast Services (CBS) for allow applications to receive cell broadcast data.

Previous Home Next