The Executive Committee for SE/EE of the JCP has approved JSR 330, Dependency Injection for Java. This specification, led by Bob Lee @ Google and Rod Johnson @ SpringSource was submitted in May 09 and moved through the JCP process very quickly. The final vote result was 14-1-1. Congratulations to the leads and the EG on this important spec. There are still a few specs left to approve that will go into the umbrella JavaEE 6 JSR. The next major one is probably JSR 299, which was submitted ahead of 330 but was later restructured to leverage it.

As previously reported last month, JavaEE 6 will include JSR330 and JSR299. Roger Kitain already has a simple yet detailed blog entry on using JCDI (JSR 299, ex-WebBeans) in GlassFish. He walks through JSF 2.0 and JSR 299/JSR 330 code. You'll see there @Inject, @Qualifier, @SessionScoped, @ApplicationScoped, all in action.

If you're curious enough to test this sample, I would recommend using NetBeans 6.8 M1 - register a recent GlassFish v3 build (promoted build web 62 for instance), create a Web Application with Java EE 6 as the platform level and copy paste the various pieces. No further settings are required.

Overall, this shows progress since Cay's previous entry on the topic. Other posts on similar topics are marked with the "jsr299" and "jsr330" tags. Keep an eye on Roger's blog for more entries on this topic.

Java EE 6 will include JSR 330 and JSR 299. Roberto explains the changes: • JSR-299 will be updated to use the JSR-330 annotations • JSR-330 has evolved to take into account requirements from JSR-299 • Both JSRs will be part of the Java EE 6 Platform

Thanks to everybody that worked so hard to make these changes; obviously we wished this had happened earlier in the Java EE 6 cycle but the result will be an improved platform. We estimate that the final release of Java EE 6 (and GFv3) will be around November but we should have specific dates next week.

Check out Roberto's Announcement for details.

The JCP EE/ES EC has approved JSR 330 (Dependency Injection for Java). The vote was 14 YES, 1 ABSTAIN (Red Hat) and 1 didn't vote (Nortel). Sun, Ericsson, IBM, Red Hat and Oracle all requested coordination between JSR330 and JSR299 (WebBeans). Check out the Vote Comments for the different positions.

Better late than never, I guess. Everybody (JCP as well as JSR 330 submitters) have committed to transparency, so we will be able to follow-up the evolution of this story. And consider Joining the JCP to influence this and other standards in your platform.

Three brief but important JCP news:

The JCP also approved additional transparency for JCP 2.7, which I believe is a very important part in running an Expert group for a number of reasons, including balancing the role of the EG lead.

The final news is the submission of JSR 330, Dependency Injection for Java. The relationship to JSR 299 is unclear to me at this point.