Hibernate.orgCommunity Documentation

Chapter 12. Annotation Processor

12.1. Prerequisites
12.2. Features
12.3. Options
12.4. Using the Annotation Processor
12.4.1. Command line builds
12.4.2. IDE builds
12.5. Known issues

Have you ever caught yourself by unintentionally doing things like

Then the Hibernate Validator Annotation Processor is the right thing for you. It helps preventing such mistakes by plugging into the build process and raising compilation errors whenever constraint annotations are incorrectly used.

Tip

You can find the Hibernate Validator Annotation Processor as part of the distribution bundle on Sourceforge or in the usual Maven repositories such as Maven Central under the GAV org.hibernate:hibernate-validator-annotation-processor:5.1.1.Final.

The Hibernate Validator Annotation Processor is based on the "Pluggable Annotation Processing API" as defined by JSR 269 which is part of the Java Platform since Java 6.

As of Hibernate Validator 5.1.1.Final the Hibernate Validator Annotation Processor checks that:

The behavior of the Hibernate Validator Annotation Processor can be controlled using the processor options listed in table Table 12.1, “Hibernate Validator Annotation Processor options”:


This section shows in detail how to integrate the Hibernate Validator Annotation Processor into command line builds (javac, Ant, Maven) as well as IDE-based builds (Eclipse, IntelliJ IDEA, NetBeans).

When compiling on the command line using javac, specify the JAR hibernate-validator-annotation-processor-5.1.1.Final.jar using the "processorpath" option as shown in the following listing. The processor will be detected automatically by the compiler and invoked during compilation.


There are several options for integrating the annotation processor with Apache Maven. Generally it is sufficient to add the Hibernate Validator Annotation Processor as dependency to your project:


The processor will then be executed automatically by the compiler. This basically works, but comes with the disadavantage that in some cases messages from the annotation processor are not displayed (see MCOMPILER-66).

Another option is using the Maven Annotation Plugin. To work with this plugin, disable the standard annotation processing performed by the compiler plugin and configure the annotation plugin by specifying an execution and adding the Hibernate Validator Annotation Processor as plugin dependency (that way the processor is not visible on the project's actual classpath):


Do the following to use the annotation processor within the Eclipse IDE:

  • Right-click your project, choose "Properties"

  • Go to "Java Compiler" and make sure, that "Compiler compliance level" is set to "1.6". Otherwise the processor won't be activated

  • Go to "Java Compiler - Annotation Processing" and choose "Enable annotation processing"

  • Go to "Java Compiler - Annotation Processing - Factory Path" and add the JAR hibernate-validator-annotation-processor-5.1.1.Final.jar

  • Confirm the workspace rebuild

You now should see any annotation problems as regular error markers within the editor and in the "Problem" view:

The following steps must be followed to use the annotation processor within IntelliJ IDEA (version 9 and above):

  • Go to "File", then "Settings",

  • Expand the node "Compiler", then "Annotation Processors"

  • Choose "Enable annotation processing" and enter the following as "Processor path": /path/to/hibernate-validator-annotation-processor-5.1.1.Final.jar

  • Add the processor's fully qualified name org.hibernate.validator.ap.ConstraintValidationProcessor to the "Annotation Processors" list

  • If applicable add you module to the "Processed Modules" list

Rebuilding your project then should show any erronous constraint annotations:

Starting with version 6.9, also the NetBeans IDE supports using annotation processors within the IDE build. To do so, do the following:

  • Right-click your project, choose "Properties"

  • Go to "Libraries", tab "Processor", and add the JAR hibernate-validator-annotation-processor-5.1.1.Final.jar

  • Go to "Build - Compiling", select "Enable Annotation Processing" and "Enable Annotation Processing in Editor". Add the annotation processor by specifying its fully qualified name org.hibernate.validator.ap.ConstraintValidationProcessor

Any constraint annotation problems will then be marked directly within the editor:

The following known issues exist as of May 2010:

  • HV-308: Additional validators registered for a constraint using XML are not evaluated by the annotation processor.

  • Sometimes custom constraints can't be properly evaluated when using the processor within Eclipse. Cleaning the project can help in these situations. This seems to be an issue with the Eclipse JSR 269 API implementation, but further investigation is required here.

  • When using the processor within Eclipse, the check of dynamic default group sequence definitions doesn't work. After further investigation, it seems to be an issue with the Eclipse JSR 269 API implementation.