Today, Red Hat submitted the final draft of JSR-299, which now goes under the moniker CDI (Contexts and Dependency Injection), along with the Reference Implementation and TCK. Check out the spec and Javadoc.
That's now official, the Bean Validation specification has been voted YES by the JCP expert committee. That's the culmination of two and a half years of work. (I know the vote has ended nov 2nd but nobody told me ;) )
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.