Hibernate Validator & Bean Validation TCK
Hibernate Validator 5.x is the reference implementation for JSR 349 - Bean Validation 1.1 of which Red Hat is the specification lead.
JSR 349 - Bean Validation defines a metadata model and API for JavaBean validation as well as method validation. The default metadata source are annotations, with the ability to override and extend the meta-data through the use of XML validation descriptors. The API is not tied to a specific application tier or programming model. It is specifically not tied to either the web tier or the persistence tier, and is available for both server-side application programming, as well as rich client Swing application developer.
Together with the reference implementation, Hibernate provides also the Bean Validation TCK. You can find more information about the TCK here.
For more information regarding the specification itself refer to beanvalidation.org.
All artifacts described here, namely Hibernate Validator 5 as well as Bean Validation API and TCK are provided and distributed by JBoss (Red Hat) under the Apache Software License 2.0.
Hibernate Validator Annotation Processor
Have you ever unintentionally done one of the following:
- Annotated a bean property with a constraint which does not have a constraint validator for this type (e.g. by annotated a String with @Past)
- Annotated the setter of a JavaBean property instead of the getter
- Annotated static fields or methods with constraint annotations
Then the Hibernate Validator Annotation Processor is the right thing for you. It is an annotation processor based on JSR-269 which plugs into the build process and raises compilation errors whenever constraint annotations are incorrectly used. Read more about this processor here. It is available in the JBoss Maven Repository.
Hibernate Validator News
- Hibernate Validator 5.0.1 and the story behind the "missing" 5.0.0.Final
- May 2, 2013 5:00 AM by Hardy Ferentschik
- Today we are happy to announce the 5.0.1.Final release of Hibernate Validator. In case you are wondering what happened with 5.0.0.Final - it has not gone missing. In fact it was released on the 11th of April. The long story is, that we had to release 5.0.0.Final to meet the Java EE 7 release sch…