Bean Validation 1.1 officially reaches the JCP

by Emmanuel Bernard on 28 Mar 2012 release

Bean Validation 1.1 early draft 1 officially reaches the JCP and is available on their website. You already knew about it from the release and artifacts announcements.

That's still a significant milestone that has to be reached by the JCP rules. A specification needs to produce a certain amount of output which is regulated by the JCP itself. If you are curious, I encourage you to read the process document.

Note that JSR-349 (Bean Validation 1.1) does run under the previous version of this process but in practice we obey the rules of the current version (especially in openness).


Code artifacts published for Bean Validation 1.1 early draft 1

by Emmanuel Bernard on 16 Mar 2012 release

Following the release of the first early draft for Bean Validation 1.1, we have published the code artifacts:

  • the code source
  • the jar
  • the JavaDoc

All are available on JBoss's Maven repository. Alternatively, you can reference them in your Maven POM




Bean Validation 1.1 early draft 1 is out - time for feedback

by Emmanuel Bernard on 13 Mar 2012 release

After a long time in the shadows of open work... Ahem, take two. After a long time at work, I am very pleased to announce Bean Validation 1.1 early draft 1. This is our first big milestone since the release of 1.0.

The draft is making its way through the official channels of the JCP but we also wanted to release it in full openned. For people in a hurry, the spec draft is here.

What's new

We worked on three major areas:

  • openess
  • method level validation
  • dependency injection


The specification, the reference implementation, the TCK, this website... everything is open sourced. All work done on Bean Validation 1.1 is done in the open either on the mailing list, the issue tracker or via GitHub pull requests. Check out more in the how to contribute section.

Method-level validation

You can now put constraints declarations on parameters and return values of methods and constructors.

public class OrderService {

    public OrderService(@NotNull CreditCardProcessor creditCardProcessor) {

    public void placeOrder(
        @NotNull @Size(min=3, max=20) String customerCode,
        @NotNull @Valid Item item,
        @Min(1) int quantity) {


Interception frameworks like CDI will check these constraints upon method calls thanks to the @MethodValidated annotation. Read more in the spec.

Dependency injection

Bean Validation uses a few components MessageInterpolator, TraversableResolver, ConstraintValidatorFactory and most importantly ConstraintValidator. We have standardized how these objects are managed by a container and how these objects can benefit from container services.

That means that your constraint validator implementation will be able to get resources injected automatically.

While we go into details on how it will fit in CDI and Java EE, we have worked hard to make it container agnostic. If you write or use other containers (Guice, Spring Framework, Avalon :) ), check out if it fits properly.


We have had tremendous help from the Bean Validation community at large but I would like to give a massive thank you to Gunnar Morling who stepped up and lead the work on method-level validation. This is by far the biggest new feature of Bean Validation 1.1.

How to read the spec and provide feedback

The draft has been published here and all changes are marked with a different color. Green for additions, yellow for changes and struck through red for removals . This will help you see what has changed precisely.

Have feedback? Please talk to us either:

If you want to go to the next step and contribute, send us an email to the mailing list and read how to contribute.


Proposal for method validation added

by Gunnar Morling on 01 Feb 2012 proposal

The first draft of the proposal for method-level validation is online. The proposal covers the declaration of parameter as well as return values constraints, extensions to the Validator API, related additions to the meta-data API etc.

So check out the proposal document and let us know what you think, e.g. by sending your questions or remarks to the beanvalidation-dev mailing list.