Skip to main content

Bean Validation (JSR 303) using Hibernate Validator in Spring Boot

Bean Validation
Bean validation has always been a tremendous effort in Java based Enterprise application development. Java Bean Validation (JSR 303) is the framework that defines how Java Beans should be validated. There are few validator APIs that support JSR 303. Hibernate validator is the most popular among them. It helps validate Java Beans using annotation and the beans can be validated at presentation layer, service and data access layer. Hibernate validator also offers custom validation, cross field validations. You can checkout the latest hibernate validator documentation for built-in validator annotations.

Assumption      : Spring Boot (1.5.6),  Hibernate Validator(5.4.1.Final), Maven Projects

Integrating Spring Boot & Hibernate Validator
Spring Boot offers built-in starter dependency management for most of the frameworks and APIs available in Java Application Development. It has support for bean validation using hibernate validator API. The discussion focuses on how to validate presentation layer by Hibernate Validator using Spring Boot.

Step 1: Spring Boot has a starter validation that inherits hibernate validator. All we need to do is to add this starter dependency in pom.xml for spring boot application.


As soon as we add this dependency, Spring Boot will download and be aware of hibernate validator and we can use it to validate the beans in presentation layer which is Spring MVC in our case.

Step 2: Enable constraint annotations on Java Beans. Below example shows how to add annotations to validate the constraint on the fields. The naming of the message will be always ConstraintName.BeanName.PropertyName.

 public class EmployeeForm implements Serializable {

  private String id;

  @Size(min = 1, max = 50, message = "{Size.employeeForm.firstName}")
  private String firstName;

  @Size(min = 1, max = 50, message = "{Size.employeeForm.lastName}")
  private String lastName;

  @NotBlank(message = "{NotBlank.employeeForm.dob}")
  private String dob;

  @NotBlank(message = "{NotBlank.employeeForm.gender}")
  private String gender = Gender.MALE.getCode();

  @NotBlank(message = "{}")
  @Email(message = "{}")
  private String email;

Step 3: To validate the form (Java Bean) in presentation layer (Spring MVC), we have to add @Valid annotation in the controller mapping like below. That will do all the tricks to validate the field constraints. Pretty simple. isn't it?

    @PostMapping(value = "/employees/")
    public String createEmployees(@Valid @ModelAttribute("newEmployeeForm") 
                  EmployeeForm employeeForm, BindingResult result, ModelMap model) {
        if (result.hasErrors()) {        
            model.addAttribute("employeeFormError", Boolean.TRUE);
            return ADD_EMPLOYEES;
        return "redirect:/employees/";

Hibernate Validator has only limited built-in constraints but it has extensibility. We can create our own constraints to suit the needs. 


Popular posts from this blog

CSRF enabled Ajax requests using Spring Security

Many of you who have worked on Spring Security might be aware of the fact that Spring Security protects applications from Cross Site Request Forgery using _csrf tokens in the request sent to the web server. You can find a detailed understanding in the Spring documentation page. The objective of this post is to explain how to send _csrf tokens in the Ajax requests when we protect our application URL and application access using spring security.

How to get CSRF tokens
While we submit a form using an application that is protected with Spring Security, the form gets a default hidden parameter in the form body when using <form:form> element. The param contains the _csrf tokens to authenticate the requests in the server. In case we use other ways to create forms, we have to manually include a hidden parameter that contains name as ${_csrf.parameterName} and  value as ${_csrf.token}. For example,

In-Place editing with X-Editable using Datatable plugin

In-place editing is a trending feature that can be seen in many latest web applications, a popular example would be where the editing data happens on the web page without any explicit forms or popups. Another such example I could point out is, The in-place editing is very nice in such a way that editing data seems so natural and user friendly.

To enable in-place editing, there are many free JQuery plugins available on the internet. We are discussing a very popular plugin called x-editable. Most of the time we use html tables to display data where in-place editing is enabled. Hence we need another plugin to elegantly display tables with enormous data. We use a famous JQuery plugin called datatable. Both of these plugins are used widely and free to use.

Assumption      : Bootstrap 3, JQuery used Projects

In order to enable datatable features on any ordinary table found on web page, we should initialise datatable plugin for that table. I…

Thymeleaf th:remove vs th:if Processors

Interestingly Makinus team encountered a scenario where the team has to choose between th:remove and th:if processors. The situation is like this. Makinus team worked on a project and the team lead suggested to go with #Thymeleaf template instead of decades old JSP. Hence it adopted Thymeleaf and Thymelead Layout framework to do layout-ing.

Thymeleaf Layout
Thymeleaf layout is a framework that helps doing the layout work just as tiles framework does it using JSP technology. The framework has 5 processors, important of which is layout:decorate. The processor layout:decorate works in the layout-content template model where the content template is a small piece of template that replaces content part of the layout template. This works as if parent/child templating mode where parent will define layout format while the child template replaces only the specified content portions.

Head Element Merging Strategy
Thymeleaf layout uses a special strategy to merge parent and child template <head…