Welcome to the September edition of the JCP column! Each month you can read about the Java Community Process: newly submitted JSRs, new draft specs, Java APIs that were finalized, and other news from the JCP. This month we'll discuss the elections for the Executive Committees, three new JSRs for the J2ME technology, and news about the Community's first JSR.

Maintenance Review for JSR 1
In December of 1999, IBM got the JCP underway with its first JSR: the Real-Time Specification for Java. Since then the spec leadership changed hands to TimeSys Corporation. Now this JSR is back in the news with its recent completion of a maintenance draft review with the accompanying maintenance release coming shortly. The goal of the review is to clarify many portions of the spec and to make minor API changes to correct aspects of the RTSJ that were unstable.

The Java Virtual Machine Specification
A second JSR that is in the maintenance review stage is JSR 924. It highlights the changes that are needed as part of the imminent J2SE 5.0 platform release, calling out several changes to class file formats, instruction set, and loading and linking.

Three New JSRs for the J2ME Technology
Originally submitted on June 1, JSR 246 (Device Management API) was approved by the ME EC after a so-called JSR Review Reconsideration Ballot. This proposed optional package for J2ME CLDC configurations, led by Siemens, provides a generic interface to the device management implementation in a device. It provides access to native device management protocols and to other functionality in the device such as triggering management sessions and change notification. JSR 246 is related to JSR 232 wherein the former's scope is CLDC and the latter's is CDC. Close collaboration between the spec leads is expected.

Vodafone and Nokia have jointly submitted JSR 248 (Mobile Service Architecture for CLDC) and also JSR 249 (Mobile Service Architecture for CDC). JSR 185 set a baseline for what a complete collection of Java technology for mobile devices should look like. As such it focused on CLDC/MIDP environments. JSR 249 plans to do the same thing but is now focused at the very high end of the market, the most capable devices currently available, and is using the CDC configuration with the Foundation Profile as a starting point. The expert group plans to deliver a specification for such devices and a road map document providing the future technical direction. Closely related to this effort is, of course, JSR 248, which picks up the course set by JSR 185 for CLDC/MIDP-based devices, focusing specifically on high-volume handsets. Both JSRs are scheduled to complete by September 2005.

Early Draft Review
In JCP 2.6 all draft spec reviews are publicly accessible, including what used to be the Community Review and is now called Early Draft Review. One such review is currently underway for JSR 223, Scripting Pages in Java Web Applications. The JSR makes it possible for scripts to access and manipulate Java objects and for scripting pages to be used by Java server-side applications.

The EC Elections Are Coming Up!
Autumn is near and so are the yearly elections for the two Executive Committees. But before delving deeper I say "Thank you!" to Richard Monson-Haefel. Richard was elected last year to the SE/EE EC as an individual member. Richard has since found employment with an analyst firm and felt that continuing as an individual member on the EC created the potential for a conflict of interest; a decision we must respect. Richard's seat will remain empty until the elections. For the ME EC three nominated seats are coming up: Insignia, RIM, and Sony; and two elected seats: Intel and Texas Instruments. For the SE/EE EC the three nominated seats that are expiring are Apache, Borland, and SCO; and the elected seats are Macromedia and Nokia Networks. The ratification vote on Sun-nominated seats begins on October 1 and the open election begins on November 1. Terms are three years with no limit on the number of terms.

That's it for this month. I'm very interested in your feedback. Please e-mail me with your comments, questions, and suggestions.