Apache BVal provides an implementation of the Java Bean Validation (JSR303) Specification which is TCK compliant and works on Java SE 5 or later.

Apache BVal artifacts are distributed in source and binary form under the terms of the Apache License, Version 2.0. See the included LICENSE and NOTICE files included in each artifact for additional license information. Please read the Verifying Releases section below on how to verify the integrity of downloaded files.

Current Release

Apache BVal 0.5 - Released September 21, 2012

Module Artifact Signatures Comments
Source Distribution bval-parent-0.5-source-release.zip asc md5 sha1 -
Core Framework bval-core-0.5.jar asc md5 sha1 -
JSR303 Implementation bval-jsr303-0.5.jar asc md5 sha1 javax.validation.spi.ValidationProvider (requires bval-core)
Implementation Bundle org.apache.bval.bundle-0.5.jar asc md5 sha1 javax.validation.spi.ValidationProvider w/ OSGi metadata (includes bval-core and bval-jsr303)
Google Guice Integration bval-guice-0.5.jar asc md5 sha1 Optional integration module
Extra Routines and Constraints bval-extras-0.5.jar asc md5 sha1 Optional module
Legacy Agimatec JSON support bval-json-0.5.jar asc md5 sha1 Optional integration module
Legacy Agimatec XML support bval-xstream-0.5.jar asc md5 sha1 Optional integration module

Older Releases

Apache BVal 0.4 - Released April 13, 2012

Available at the Apache release archive.

Apache Bean Validation 0.3-incubating - Released April 28, 2011

Available at the Apache release archive.

Apache Bean Validation 0.2-incubating - Released August 18, 2010

Available at the Apache release archive.

Apache Bean Validation 0.1-incubating - Released June 11, 2010

Available at the Apache release archive.

Maven Users

Our artifacts are published to the Maven Central repository and can be found under the org.apache.bval groupId.

You'll need to add the following dependencies in your builds (and Maven will automatically include the additional transitive dependencies for you):


Maven will determine the transitive dependencies for the artifacts, but if you are not using Maven to build your project, then you will also need the following dependencies on the classpath:


Verifying Releases

It is essential that you verify the integrity of any downloaded files using the PGP or MD5 signatures. For more information on signing artifacts and why we do it, check out the Release Signing FAQ.

The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the artifact. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures using:

$ pgpk -a KEYS
$ pgpv bval-parent-0.5-source-release.zip.asc


$ pgp -ka KEYS
$ pgp bval-parent-0.5-source-release.zip.asc


$ gpg --import KEYS
$ gpg --verify bval-parent-0.5-source-release.zip.asc

Alternatively, you can verify the MD5 signature on the files. A Unix/Linux program called md5 or md5sum is included in most distributions. It is also available as part of GNU Textutils. Windows users can get binary md5 programs from these (and likely other) places: