Javalobby
spacer James Sugrue
  • Bio
  • Website
  • @dzonejames
  • spacer

I've been a zone leader with DZone since 2008. I work as a technical lead on a next generation tool suite using based on Eclipse. This means that I get to use Java everyday, and a selection of the best Eclipse technologies, from EMF to GEF to Xtext. Along with all of this, I do iOS development in my spare time. James is a DZone Zone Leader and has posted 545 posts at DZone. You can read more from them at their website. View Full User Profile

The Java Community Process - A Year in Review

05.18.2009
spacer Email
Views: 23937
  • Tweet
  • spacer

We Recommend These Resources

Getting Started with FUSE Mediation Router

Getting Started with Apache Camel - 6/28/2012 - 10:00AM EST

Micro Focus SilkTest 2011

The Java Evolution Mismatch: Why You Need a Better JVM

DevOps: From Concepts to Practical Applications Featuring Forrester Research, Inc. and Equinox

Last year the Java Community Process turned 10 years old. Patrick Curran has published his review of the last year of activity in JSR Watch: Here's To Progress. In the article he discussed a number of issues from the JCP membership and leadership to JSR activity.

JSR Activity 

One of the most interesting things for me is that in all of the 70 JSRs that are active right now, the majority of them are focussed on JavaME, which has 27. JavaSE has 20, which JavaEE has 15. 

The new JSRs were JSR 320: Services Framework (AT&T); JSR 321: Trusted Computing API for Java ( IAIK Graz University of Technology); JSR 322: Java EE Connector Architecture 1.6 (Sun); JSR 325: IMS Communication Enablers (ICE) (Ericsson AB); JSR 326, Post mortem JVM Diagnostics API (IBM); and JSR 327: Dynamic Contents Delivery Service API for Java ME (SK Telecom).

 

The JSR lifecycle is certainly varied, and it's good to see that the committee are committed to helping complete JSRs faster:

The time it took these JSRs to work their way through the process varied from a little over one year for JSR 291 to five years for JSR 190. There are obviously lessons to be learned about how to - and how not to - complete JSRs quickly, and we will investigate further over the coming months.

 

Out of the 70 active JSRs, Sun (unsurprisingly) holds the Spec Lead role for most, at 27. They are followed by Nokia (11), Oracle (8), Motorola (5) and IBM (4). With Oracle buying out Sun, I guess that puts Oracle out front with 35.  50% spec leadership would give them a significant say in the future of Java.

 

New Initiatives

Probably one of the most important things for Java developers is that the Expert Groups are being encouraged to work in an open and transparent manner, and the Executive Committee are to do the same:

Starting in September 2008 the ECs agreed to make full minutes and meeting materials accessible to the general public rather than simply posting summaries that only JCP members could read. (We reserve the right to go into Private Session from time to time when sensitive matters are discussed, but we don't expect to do this very often.) If you want to see what we're up to, the meeting materials are accessible.

Membership of the JCP has increased by 3%, with about a quarter of the members being corporations. 

So, we've seen 10 years pass on the JCP now - are there any other changes that you would like to see happen? Does the JSR model still work?

 

References
Reference: 
JSR Watch: Here’s to Progress
Tags:
  • Java
  • JCP
  • JSR
Published at DZone with permission of its author, James Sugrue. (source)
  • DZone
    • Refcardz
    • Book Reviews
    • Tech Library
    • IT Questions
    • Snippets
gipoco.com is neither affiliated with the authors of this page nor responsible for its contents. This is a safe-cache copy of the original web site.