- Notifications
You must be signed in to change notification settings - Fork582
Hibernate Validator - Jakarta Validation Reference Implementation
License
hibernate/hibernate-validator
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Version: 9.0.0.Final - 2025-05-20
This is the reference implementation ofJakarta Validation 3.1.Jakarta Validation defines a metadata model and API for JavaBean as well as method validation.The default metadata source are annotations, with the ability to override and extendthe metadata through the use of XML validation descriptors.
The documentation for this release is included in thedocs directory of the distribution package or can be accessedonline.
The full list of changes for this release can be found in changelog.txt.
JDK 17 or above.
In case you use the distribution archive from the download site, copydist/hibernate-validator-<version>.jar together with alljar files fromdist/lib/required into the classpath of your application. For the purposes of logging, Hibernate Validator usesthe JBoss Logging API, an abstraction layer which supports several logging solutions such (e.g. log4j or the logging frameworkprovided by the JDK) as implementation. Just add a supported logging library to the classpath (e.g.log4j-<version>.jar) and JBossLogging will delegate any log requests to that provider.
Add the following artifact to your Maven/Ivy/Gradle dependency list:
<dependency> <groupId>org.hibernate.validator</groupId> <artifactId>hibernate-validator</artifactId> <version>9.0.0.Final</version> </dependency>
You also need an API and implementation of the Unified Expression Language. These dependencies must be explicitly added in an SE environment.In a Jakarta EE environment, they are often already provided.
<dependency> <groupId>org.glassfish.expressly</groupId> <artifactId>expressly</artifactId> <version>6.0.0</version> </dependency>
Jakarta Validation defines integration points withCDI. If your application runsin an environment which does not provide this integration out of the box, you may use the Hibernate Validator CDI portableextension by adding the following dependency:
<dependency> <groupId>org.hibernate.validator</groupId> <artifactId>hibernate-validator-cdi</artifactId> <version>9.0.0.Final</version> </dependency>
hibernate-validator-annotation-processor-<version>.jar is an optional jar which can be integrated with your buildenvironment respectively IDE to verify that constraint annotations are correctly used. Refer to theonlinedocumentation for more information.
Hibernate Validator itself as well as the Jakarta Validation API and TCK are all provided and distributed underthe Apache Software License 2.0. Refer to license.txt for more information.
You can build Hibernate Validator from source. Refer to theContributing to Hibernate Validator guide for more information.
The official Continuous Integration service for the project is hosted onci.hibernate.org.
We also include aGitHub action build file that can be used by those interested inrunning builds on their own forks.This build runs on Linux and Windows and executes the TCK both in standalone and in containermodes.
About
Hibernate Validator - Jakarta Validation Reference Implementation
Topics
Resources
License
Code of conduct
Security policy
Uh oh!
There was an error while loading.Please reload this page.