Posted by robc
on December 1, 2009 at 4:48 PM PST
Today the JCP Executive Committee approved the Java EE 6 platform specification.
With the closing of the final approval ballot earlier today, it is now official: the JCP Executive Committee has given a green light to the release of the Java EE 6 platform specification. The final release will happen on December 10, when GlassFish v3 will be available. For more details of the ballot, with comments from several EC members, please refer to the JCP web site . Of course the excitement of the event drove me to watch live the ballot close at midnight PT and tweet about it!
Several other Java EE component JSRs were approved at the same time: Servlet 3.0, JPA 2.0, EJB 3.1, Connector 1.6, CDI 1.0. All other components, be they full JSRs or maintenance releases (MRs, for insiders), had been previously approved. I should also mention here that, being part of the platform JSR (JSR-316) the Java EE 6 Web Profile too was approved, and so was the Managed Beans 1.0 specification I talked about in prior blog entries. So, yes, now we really have profiles in Java EE: let's put them to good use!
We are going to have more white papers, tutorials, etc. coming up for the final release in a few days. In the meantime, even a casual perusal of the javadocs will show a number of new APIs in key areas: JAX-RS, Dependency Injection, CDI, Bean Validation. I see a bright future for these APIs, and fully expect them to become key components of Java EE applications in the coming years. I also happen to think that the level of integration that we achieved between these new APIs and some of the existing ones represents a valuable principle that can guide the evolution of Java EE going forward; certainly I expect future Java EE APIs to be held to the same strict criteria for integration with the rest of the platform that JAX-RS, Bean Validation and CDI were held to in this release.
It's been a long journey, so I'd like to take this opportunity to thank everybody who contributed to this release over the years, whatever form their contributions took. Naturally, one tends to focus on expert group members -- after all, they get the coveted (?) mention of their name in the specification itself in exchange for years of toil on the mailing list -- but with the continuous increase in the transparency of the process and the use of open source for the reference implementation, it turns out that there are many, many more contributors than the usual suspects. So, whether you sent feedback to the expert group, reported an issue in the implementation, asked a question on one of the GlassFish mailing lists that led us to realize we had overlooked something, or spoke to me at a conference or some other event to describe your experience with the technology and suggest improvements, please accept my most heartfelt thanks.
Now let's enjoy Java EE 6!