Tuesday Jun 09, 2009

JSR 330 (Dependency Injection for Java) Accepted by the JCP


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.

Wednesday May 27, 2009

JCP News: JSF 2.0, JCP 2.7 and @Inject JSR

Three brief but important JCP news:


The first JavaEE 6 specification has been Approved by the EC. JSF 2.0 was approved by a vote of 12 YES, 0 NO, 0 Abstain... and 4 EC members not voting (if you are curious about these things, check out the EC Voting Records). Other JSRs should come along in the near future as we close on Java EE 6.

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.