From Within the Java Community Process Program
From Elections to Final Ballots
Welcome to the December edition of the JCP column! Every 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 I'll cover how the elections are progressing, and a new JSR from Sun, two JSRs in Community Review, two in Public Review, and three on the Final Approval ballot.
The Executive Committee Elections, the Open Election Stage
This time there are two seats on each EC open for election. When you look at the candidates on the election Web site at http://jcpelection2003.org, you'll see that things look a little different compared to previous years. For the SE/EE EC there are nine candidates running for the two available seats. While that number is not remarkable, the fact that eight of the nine are individual members is remarkable. Doug Lea, the sitting EC member, is running as well as Larry Cable, Gustavo Alvarado, Dong Chen, Dave Marquard, Selvan Rajan, Huy Nguyen, and Richard Monson-Haefel. The one corporate member is Sonic Software. For the ME EC, five candidates are running for the two available seats. Selvan Rajan is also running for a seat on this EC and he is joined by Ericsson, Esmertec, PalmSource, and Intel. The elections closed on November 17 and the results were announced on the 18th (after this magazine had gone to press).
In last month's ratification vote all candidates were approved by the JCP membership. I congratulate IBM, HP, Fujitsu, Oracle, Motorola, Siemens, and Matsushita on their reelection and welcome Vodafone to the ME EC.
A New JSR for the J2EE Environment
JSR 233, J2EE Mobile Device Management and Monitoring Specification, is currently in the JSR Review stage. In short, this JSR proposes a facility on top of the J2EE platform to remotely manage and monitor the software on a mobile device. Two examples of areas where there is a need for this functionality are enterprises that enable their workforce to interact with enterprise information from mobile devices, and carriers providing customer support for software services on mobile devices. The JSR will have a couple of relationships with existing JSRs. JSR 232 defines a management environment on the device but not the server infrastructure. JSR 160 does define a management and monitoring structure but it depends on JSR 3, both of which are optional for J2EE environments; however, mobile devices generally do not support either one. Finally, JSR 233 aims to reuse APIs from the J2EE client provisioning JSR (# 124), which completed last month.
Two JSRs in Community Review
JSR 170, which is led by Day Software based in Switzerland, is working to define a specification for access to content repositories. Its expert group is one of the larger ones in the JCP program with 30 JCP members participating. The JSR provides an implementation-independent API to access common services that content repositories provide, such as version control, fine-grained access control, full-text search, and content categorization.
Submitted by Nokia in April of this year, JSR 212 is now in Community Review. It defines the Java API for SAMS Messaging and is destined to work in both J2SE and J2EE environments. The specification supports both short (SMS) and multimedia (MMS) messages.
Two JSRs in Public Review
The first JSR we'll cover in this section is JSR 147, Workspace Versioning and Configuration Management, led by IBM. While this JSR was submitted a while back, in the last months it has gained remarkable momentum by going through Community Review in late October and early November and subsequently entering Public Review. Collaborative authoring tools for software development, document management, and so on have a need for services to manage versioning and configuration of files and other resources. This JSR provides a client-side API and builds on several protocols (DeltaV, WebDAV, HTTP) to deliver this functionality.
The second JSR I want to cover is the J2ME-based Security and Trust Services JSR, or JSR 177, of which Sun is the Spec Lead. The collection of APIs defined here is aimed toward CLDC- as well as CDC-enabled devices.
Three JSRs Facing the Final Ballot
In the "almost final" category we have three efforts this month. Two are technology related and the third is process oriented. First off is the PDA Profile JSR led jointly by PalmSource and IBM. JSR 75 defines Java APIs for several features that PDA devices typically have, such as personal information management and file system access. The J2ME CLDC platform is the base requirement for this profile. Next is JSR 169, the JDBC optional package for the CDC+Foundation Profile. The JSR defines equivalent functionality to the java.sql package while taking into account the constraints of CDC-based devices. And last, the Program Office's own JSR, number 215, which specifies what JCP 2.6 will look like. After the JSR goes final, the Program Office needs to implement a couple of changes to the Web application that runs JCP.org in order to roll out the new version of the JCP, which we hope to do by late January, early February.
That's it for this month. I'm very interested in your feedback. Please e-mail me with your comments, questions, and suggestions.
Onno Kluyt is the director of the JCP Program Management Office, Sun Microsystems.