In Relation To

Now that Bean Validation is officially part of Java EE 6 and that Java EE6 is officially voted YES, let's see how Bean Validation integrates with the rest of the eco system.

One of the innovations we have brought to Hibernate Search is an alternative way to define the mapping information: a programmatic API.

I have been at a few conferences lately and the EE 6 wave is taking a bunch of people by surprise. Tsunami level 6. The last two examples are W-JAX and Devoxx.

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 ;) )

After many months of polishing, we are happy to release Hibernate Validator 4. This is a major milestone for Hibernate Validator with tons of new features and a spec compliance.

Here is the latest draft before sending Bean Validation (JSR 303) to final stage (in pdf[1]). For the few who don't know yet ( ;) ), Bean Validation standardizes constraint declaration, definition, validation and metadata for the Java platform. Said otherwise, add an annotation to a property and hop it's validated.

A few people have asked me to publish my slides on Bean Validation and Hibernate Search. Here we go :)

Good news!

Bean Validation's public draft has now been approved by the EC (all members voting yes except Nortel and SpringSource who did not vote).