Jakarta Validation

Constrain once, validate everywhere

Latest news Stay up to date, subscribe to the news feed.

Jakarta Validation 3.1 specification

17 February 2025

Jakarta Validation 3.1 was released earlier in 2024. What’s new in Bean Validation 3.1? The 3.1 update of the specification, compared to 3.0, brings the following changes: The minimum required Java version is...

Bean Validation 2.0 - What’s in it?

26 February 2018

While a couple of months have passed since Bean Validation 2.0 got released, the info about what’s new in the spec may still not yet have reached everyone. Here are two...

Bean Validation has a new website!

19 October 2017

Bean Validation just got a new website and we hope you will like it! New layout We developed a more modern layout based on Semantic UI. It should be easier to the eye...

What is Jakarta Validation

Jakarta Validation is a Java specification which

  • lets you express constraints on object models via annotations

  • lets you write custom constraints in an extensible way

  • provides the APIs to validate objects and object graphs

  • provides the APIs to validate parameters and return values of methods and constructors

  • reports the set of violations (localized)

  • runs on Java SE and is integrated in Jakarta EE

public class User {

    private String email;

    @NotNull @Email
    public String getEmail() {
      return email;
    }

    public void setEmail(String email) {
      this.email = email;
    }
}

public class UserService {

  public void createUser(@Email String email,
                         @NotNull String name) {
    ...
  }
}

While you can run validation manually, it is more natural to let other specifications and frameworks validate data at the right time (user input in presentation frameworks, business service execution by CDI, entity insert or update by JPA).

In other words, run once, constrain anywhere.