Apache BVal provides an implementation of the Bean Validation Specification (JSR303) 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.


Incubating Releases

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

Module

Artifact

Comments

Source

bval-parent-0.3-incubating-source-release.zip (asc, md5, sha1)

Apache Bean Validation source

Core Framework

bval-core-0.3-incubating.jar (asc, md5, sha1)

Apache Bean Validation core framework

JSR303 Implementation

bval-jsr303-0.3-incubating.jar (asc, md5, sha1)

Apache Bean Validation JSR303 provider (requires bval-core)

Implementation Bundle

org.apache.bval.bundle-0.3-incubating.jar (asc, md5, sha1)

Apache Bean Validation provider w/ OSGi metadata (contains bval-core and bval-jsr303)

Google Guice (optional)

bval-guice-0.3-incubating.jar (asc, md5, sha1)

Optional integration module for Google Guice

Legacy Agimatec JSON support (optional)

bval-json-0.3-incubating.jar (asc, md5, sha1)

Optional integration module for JSON support

Legacy Agimatec XML support (optional)

bval-xstream-0.3-incubating.jar (asc, md5, sha1)

Optional integration module for legacy XML support

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

Module

Artifact

Comments

Source

bval-parent-0.2-incubating-source-release.zip (asc, md5, sha1)

Apache Bean Validation source

Core Framework

bval-core-0.2-incubating.jar (asc, md5, sha1)

Apache Bean Validation core framework

JSR303 Implementation

bval-jsr303-0.2-incubating.jar (asc, md5, sha1)

Apache Bean Validation JSR303 provider (requires bval-core)

Implementation Bundle

org.apache.bval.bundle-0.2-incubating.jar (asc, md5, sha1)

Apache Bean Validation provider w/ OSGi metadata (contains bval-core and bval-jsr303)

Google Guice (optional)

bval-guice-0.2-incubating.jar (asc, md5, sha1)

Optional integration module for Google Guice

Legacy Agimatec JSON support (optional)

bval-json-0.2-incubating.jar (asc, md5, sha1)

Optional integration module for JSON support

Legacy Agimatec XML support (optional)

bval-xstream-0.2-incubating.jar (asc, md5, sha1)

Optional integration module for legacy XML support

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

Module

Artifact

Comments

Source

bval-parent-0.1-incubating-source-release.zip (asc, md5, sha1)

Apache Bean Validation source

Core Framework

bval-core-0.1-incubating.jar (asc, md5, sha1)

Apache Bean Validation core framework

JSR303 Implementation

bval-jsr303-0.1-incubating.jar (asc, md5, sha1)

Apache Bean Validation JSR303 provider (requires bval-core)

Implementation Bundle

org.apache.bval.bundle-0.1-incubating.jar (asc, md5, sha1)

Apache Bean Validation provider w/ OSGi metadata (contains bval-core and bval-jsr303)

Google Guice (optional)

bval-guice-0.1-incubating.jar (asc, md5, sha1)

Optional integration module for Google Guice

Legacy Agimatec JSON support (optional)

bval-json-0.1-incubating.jar (asc, md5, sha1)

Optional integration module for legacy JSON support


Maven Users

Our artifacts are published to the Maven Central repository and can be found under:

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

    <dependency>
        <groupId>org.apache.geronimo.specs</groupId>
        <artifactId>geronimo-validation_1.0_spec</artifactId>
        <version>1.1</version>
    </dependency>
    <dependency>
        <groupId>org.apache.bval</groupId>
        <artifactId>org.apache.bval.bundle</artifactId>
        <version>0.3-incubating</version>
    </dependency>


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 -

    <dependency>
        <groupId>commons-lang</groupId>
        <artifactId>commons-lang</artifactId>
        <version>2.4</version>
    </dependency>
    <dependency>
        <groupId>org.slf4j</groupId>
        <artifactId>slf4j-simple</artifactId>
        <version>1.6.1</version>
    </dependency>
    <dependency>
        <groupId>commons-beanutils</groupId>
        <artifactId>commons-beanutils</artifactId>
        <version>1.8.3</version>
    </dependency>
    <dependency>
        <groupId>commons-collections</groupId>
        <artifactId>commons-collections</artifactId>
        <version>3.2.1</version>
    </dependency>


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, checkout 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.3-incubating-source-release.zip.asc
or
$ pgp -ka KEYS
$ pgp bval-parent-0.3-incubating-source-release.zip.asc
or
$ gpg --import KEYS
$ gpg --verify bval-parent-0.3-incubating-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 such places as here, here, or here.

  • No labels