There are no functional changes between CR1 and this Final release. Some minor issues in the @Min, @Max and @EmailValidator
got fixed (HV-335, HV-339) as well
as some documentation typos. We also spend some time improving the parsing and validation speed by reviewing and improving some reflection based code
(HV-340, HV-341, HV-342). Review the full release notes for details.
Antonio has written a nice article on how to use Bean Validation and Hibernate Validator 4.0 in JPA 1.0 and Hibernate 3.3 (by retrofitting what's happening automatically in JPA 2.0). He asked an interesting question at the end of his post.
It was bound to happen, the minute I announced the Wicket integration, I've received a few emails describing integrations with other frameworks (like Tapestry).
I've created a wiki page to list all frameworks integrating Bean Validation and a pointer to their documentation. Go ahead and fill it up with any active integration you are aware of. The page is here.
People following our work and vision on Bean Validation know that the ultimate goal is to get the ecosystem of Java frameworks to natively integrate Bean Validation where it makes sense. A particularly important area is the the presentation layer that should call Bean Validation to validate the values to be put in the domain model.