Welcome to the June edition of the JCP column! Each month I provide news and information about the Java Community Process: newly submitted JSRs, new draft specs, Java APIs that were finalized, and other updates from the JCP. June means it is JavaOne time, and hence this column will discuss the conference as well.
The Only Standards Body with a Version Number!
While the change from JCP 2.1 to 2.5 in October 2002 focused mainly on legal aspects such as license types for RI and TCK and the ability to do independent implementations, the proposed changes that would form version 2.6 of the process focus on the day-to-day activities in the JCP. This effort is done via JSR 215. I like to call out three areas of focus: Community Review, Expert Group formation, and TCKs. The proposal is to turn the Community Review into a public review (i.e., accessible to all, not just members) and to move the ballot after the existing Public Review. The goal is, this will lead to the JSRs entering the draft review phase sooner and that those reviews will receive more feedback. The JSR also suggests creating an observer category for expert groups. This enables the spec lead to distinguish between active participants and those who just want to stay abreast of developments while keeping the size of the group manageable for the spec lead. And expert group discussions and design decisions would be visible to interested JCP members. JSR 215 also proposes to set minimum TCK requirements for each JSR. This should lead to practical guidance to spec leads about this mandatory activity and to more uniformity across the JSRs. You can read more about this and send in feedback at http://jcp.org/jsr/detail/215.jsp. The Program Office and Executive Committee members are very interested in your views.
JCP @ JavaOne
The Program Office is organizing and hosting various activities and events at this year's conference. First, there's the Java Community Evening event on Wednesday, June 11. This is a joint event with the JINI and JXTA communities and, for the first time, the Executive Committees and the Program Office will be presenting JCP awards for Best Spec Lead and Most Innovative JSRs. The Program Office will also have a pod on the exhibition floor that will provide a great opportunity to meet us and discuss your favorite elements and perhaps least favorite aspects of the JCP. And finally, as part of the conference, there is a Birds-of-a-Feather session on the JCP.
New Developments in J2ME
Recently a handful of new JSRs were submitted by JCP members. JSRs 216 and 217 propose to update both Personal Profile and Personal Basic Profile to account for the introduction of the Project "Swing" technology in this space, which I wrote about last month. JSR 218 proposes to update CDC with enhanced support for small electronic devices that don't have or don't require a graphical user interface. JSR 219 proposes to provide similar updates to the Foundation Profile.
Three JSRs did not fare well in their respective ballots. JSRs 213 and 214 were voted down by the JCP ME EC members in their JSR Review ballot, while JSR 177 was voted down in the Community Review ballot. Their supporters are now preparing for their respective reconsideration ballots.
Another JSR was added to the collection of completed and final specifications. JSR 139, CLDC version 1.1, was declared final and is available for review and implementation.
News from J2SE and J2EE
The world of Java technology APIs for the desktop and server space enjoyed a relatively quiet month (a sign of many engineers getting ready for the JavaOne conference?). JSR 151 released a third Proposed Final Draft specification, while J2EE version 1.4 is getting nearer to final release. JSR 152, JavaServer Pages specification 2.0, has also released a third Proposed Final Draft containing various changes such as API changes, updates to the Tag Library Descriptor, I18N updates, and a few changes to the Expression Language. JSR 109, Web Services for J2EE, has entered a second maintenance review.
Ballot Voting Is Public At the beginning: JSR Review ballot
Halfway: Community Review ballot
At the end: Final Approval ballot.
In this column I've spoken a few times about ballots. The Executive Committees vote three times during the life of a JSR on the JSRs assigned to them:
These ballots are public. To see how EC members voted on a JSR's ballot, go to the JSR's page on JCP.org (e.g., http://jcp.org/jsr/detail/215.jsp for JSR 215) and click on the links in the status table on the page (in this example the link called "JSR Review ballot"). If voting "yes," comments are optional. An EC member is required to enter comments when voting "no" and encouraged to do so when abstaining.
That's it for this month. I am very interested in your feedback. Please e-mail me with your comments, questions, and suggestions.
About The Author
Onno Kluyt is the director of the JCP Program Management Office, Sun Microsystems.