Calling all J2ME Developers - Important J2ME JSRs To Keep Track Of

by C. Enrique Ortiz, April 9, 2005

Currently there are around 70 J2ME JSRs in the Java Community Process (JCP), some already defined and productized, others in the process of being defined, while others rejected. Some of these JSRs are related to CLDC and MIDP, others to CDC and its profiles, others define specific APIs (optional packages), while others define the handset architecture and what a mobile handset must provide.

All JSRs are important, but there are four J2ME JSRs that will define the future of J2ME in a huge way, and deserve special attention from the J2ME developer community:

  1. JSR 232 Mobile Operational Management
    Description: Create a predictable management environment for mobile devices capable of installing, executing, profiling, updating, and removing JavaTM and associated native components in the J2METM Connected Device Configuration.
    Spec Lead: Jon Bostrom , Nokia Corporation, and Harry Prabandham, Motorola
  2. JSR248 Mobile Service Architecture for CLDC
    Description: This JSR creates a mobile service architecture and platform definition for the high volume wireless handsets continuing the work started in JSR-185 and enhancing the definition with new technologies.
    Spec Leads: Mark Duesener, Vodafone Group Services Limited, and Asko Komsi, Nokia Corporation
  3. JSR 249 Mobile Service Architecture for CDC
    Description: This JSR creates a platform definition for the advanced mobile handsets and builds on the J2ME Foundation Profile specification and other JSRs as will be selected.
    Spec Lead: Mark Duesener, Vodafone Group Services Limited, and Asko Komsi, Nokia Corporation
  4. JSR 271 Mobile Information Device Profile 3
    Description: This JSR will specify the 3rd generation Mobile Information Device Profile, expanding upon the functionality in all areas as well as improving interoperability across devices.
    Spec Lead: Jim Van Peursem, Motorola

It is very important that dev. community's input gets to the EGs early in the JCP process. If this can't happen, make sure you provide your input when the JSR enters the public review phase. JSRs 248/249 and 271 are still in the initial phases of definition, so it would be great to capture the dev. community's input now and pass that to the EG as soon as possible. For JSR 271 (MIDP3) feedback has already been captured in the MIDP3 wish list Wiki. The J2ME Dev. community Wiki will continue to serve as a central repository/collaboration tool to capture JSR feedback from the dev community, and the Weblog to announce any news. Please participate and provide your feedback.

From my perspective, I am counting on JSR 232 to address the management aspects described in The Security Gap in Wireless Mobility (Handsets). I am counting on JSR 271 (MIDP3) to address the wish list items described in the J2ME Developer Community MIDP3 Wiki. And I am counting on JSR 248/249 to define a consistent (handset) platform that includes all the required APIs and hardware characteristics that will allow developers to create advanced business, personal and entertainment (end-to-end) applications and services, to create a JSR that doesn't leave behind important APIs such as JAX-RPC and the SATSA APIs, and to define the CLDC to CDC migration plan.

ceo