Skip to the content.

D10041 - JSR303, 2.x version

In current tutorial we have checked most of JSR303 annotation usage based on Hibernate Validator Framework. Here are some new annotations in JSR303.

You can set above new annotations in 2.x version and validated by Hibernate Validator.

Demo projects:


  1. JSR303 is only supported in Agent component in zero system, it means that after you have send the message to event bus, the JSR303 will be effectiveness.
  2. When you write the code with the Interface Style ( Will introduce in forward tutorials ), JSR303 will not support this kind of situation.
  3. For @BodyParam, it also impact Agent component only, but could support Interface Style instead of JSR303 and could provide more useful validations.

1. Source Code

package up.god.micro.validation;

import io.vertx.up.annotations.EndPoint;

import javax.validation.constraints.Email;

public class EmailActor {

    public String sayEmail(
            @QueryParam("email") final String email
    ) {
        return "Hi, email = " + email;

2. Testing

URL : http://localhost:6083/api/jsr303/email?email=xxxx

Method : GET

Response :

    "code": -60000,
    "message": "[ERR-60000] (Validator) Web Exception occus: (400) - Request validation failure, class = class up.god.micro.validation.EmailActor, method = public java.lang.String up.god.micro.validation.EmailActor.sayEmail(java.lang.String), message = must be a well-formed email address.",
    "info": "must be a well-formed email address"

If you changed the email parameter such as, you can see following response:

    "data": "Hi, email ="

3. Summary

In total, zero system support most of JSR303 specification because it used Hibernate Validator to do it. Another feature that zero system provided is that it extend JSR303 and could verify the JsonObject/JsonArray format, you can move forward to study the next annotations.