In Relation To

I put a whole bunch of work into the Javadoc for CDI recently. You can see it here. There's a good overview of the spec in the package doc for javax.enterprise.inject.

Nick Belaevski is the RichFaces dev lead in Minsk and has officially joined the JSF 2.0 Expert Group (JSR-314) along with Alex Smirnov to represent RichFaces and Exadel. As many of you know Dan Allen and Pete Muir are also on the JSF 2.0 Expert Group representing Red Hat & JBoss. Together these 4 people along with the rest of the EG will continue to help advance JSF as a standard and a technology.

Hibernate Validator 4.0.2 is now available for download. This release was necessary for the JCP integration efforts for JSR-303 and addresses a potential NullPointerException (HV-263). Refer to the 4.0.2 release notes for a full list of changes.

In my previous little rant, I showed you how to use @Alternative and alternative stereotypes to easily change bean implementations based upon deployment scenario. But that's not the end of the story. There's two other things I would sometimes like to be able to change at deployment time:

Suppose we have an external resource, a database, let's say, that we want to be able to change depending upon the deployment environment. In CDI, we declare resources using a producer field declaration.

I'm trying really hard to emphasize to the community that CDI and Weld are not just a dependency injection solution. We did not come at this from the point of view of trying to solve dependency injection, or of trying to build a better Spring.

The second release towards JPA 2 support. Specific JPA 2 related enhancements from Beta-1 include:

The 5th development snapshot of the JBoss JCA 1.6 container is out.

Dan Allen has been writing a series of articles covering ideas from Seam that made it into JSF2. The latest installment covers view parameters and creating bookmarkable links. Seam users should find this stuff extremely familiar.

CDI (JSR-299) and Weld 1.0 are almost a reality. We've got word from Sun that CDI and the rest of Java EE 6 will be submitted to the JCP on November 9. I've spent the last few days filling out the Javadoc for the CDI API and SPI packages and making some last-minute cleanups to the spec. Meanwhile, Pete and the others are fixing bugs in the RI and TCK. This process has taken more than 3 years, and an incredible amount of pain, but we're now looking at one of the most well-reviewed JCP specifications ever.