Different validation annotation rule for same Data Access Object

Question

How to customize the validation annotation based on some criteria using javax validation with Hibernate validation implementation.

Sample code:

import javax.validation.Validator;
import javax.validation.ValidatorFactory;

import java.util.Set;

import javax.validation.ConstraintViolation;
import javax.validation.Validation;

import org.springframework.stereotype.Component;

import com.kp.mechanic.workshop.validator.beans.GeoLocation;
import com.kp.mechanic.workshop.validator.beans.Practioner;
import com.kp.mechanic.workshop.validator.beans.PractionerAddress;

@Component("validator")
public class ValidatorService {

    private  Validator validator;
    private  ValidatorFactory factory;

    public void execute() {
        System.out.println(" Validation framework starts");
        try {

            //  < DAO call to get GEO Location is AUS >

            //Construct Geo Location:
            GeoLocation geoLocation= new GeoLocation();
            geoLocation.setStrtAddrLine1("walker street ");
            geoLocation.setOptionalAddrLine2("bonitoa road");
            geoLocation.setZipCD("SY");


             factory = Validation.buildDefaultValidatorFactory();
             validator = factory.getValidator();
             Set<ConstraintViolation<Object>> resultSet= validator.validate(geoLocation);

             for (ConstraintViolation<Object> object : resultSet) {
                   System.out.println(object.getPropertyPath() + ": " + object.getMessage());
               }


        }
        catch(Exception e) {
            System.out.println("Message "+e);
            e.printStackTrace();
        }

    }
}

Refer the given below POJO using Lombok.

import javax.validation.constraints.NotNull;
import javax.validation.constraints.Pattern;
import javax.validation.constraints.Size;
import lombok.Getter;
import lombok.Setter;

@Getter
@Setter
public class GeoLocation {
//City name
        @NotNull(message="warn:Missing data")
        @Size(min =3 , max =50, message = "warn:Invalid length")
        @Pattern(regexp = "^a-zA-Z",message = "warn:Invalid characters found in text",flags=Pattern.Flag.CASE_INSENSITIVE)
        private String cityNM;

        //State Code
        @NotNull(message="warn:Missing data")
        @Size(min =2 , max =2, message = "warn:Invalid Length")
        @Pattern(regexp = "^[a-zA-Z]",message = "warn:Invalid characters found in text",flags=Pattern.Flag.CASE_INSENSITIVE)
        private String stateCD;

        //zip code
        @NotNull(message="warn:Missing data")
        @Size(min =5 , max =9, message = "warn:Invalid Length")
        @Pattern(regexp = "^[0-9]",message = "warn:Invalid characters found in text")
        private String zipCD;
}

Using given above pom entries .

The above code is working fine for the given below validation rules for GEO Location is "AUS".

> CityName   : not null , minimum 3 and maximum 50 characters, only alphabets.
> State Code : not null , maximum 2 , only alphabets. 
> Zip  Code  : not null , minimum 5 and maximum 9, only digits.

Where as for "IND" , i would like to change the given below validation rules as such.

> CityName   : not null , minimum 10 and maximum 15 characters, only alphabets
> State Code : not null , maximum 6, only alphabets. 
> Zip  Code  : not null , maximum 10, only digits

Can you give any suggestion to change the validation rules based on the geo location type is IND?

This is a kind of Custom Annotation, is there any better approach to reuse the annotation without writing java logic in custom annotation class ? Custom Annotation for cross fields

You are referring to a Geo location value of `AUS`. But, which field does that refer to? There are city, state, and zip fields. — Tim Biegeleisen, Feb 12 '20 at 05:27
Geo location is POJO , i used to get the List of POJO from DAO Layer. — Vasanth, Feb 12 '20 at 05:32
select * from geo where type='AUS' , its working fine. i would like to do different kind of validation for IND ie select * from geo where type='IND' — Vasanth, Feb 12 '20 at 05:33

score 0 · Answer 1 · answered Feb 12 '20 at 05:32

First of all appreciate for a nice question.

In above scenario I would go for custom annotation based validator as shown below.

package com.example.demo;

import static java.lang.annotation.ElementType.METHOD;
import static java.lang.annotation.ElementType.FIELD;

import java.lang.annotation.Documented;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

import javax.validation.Constraint;
import javax.validation.Payload;

@Constraint(validatedBy = StateCodeValidator.class)
@Documented
@Target({METHOD, FIELD})
@Retention(RetentionPolicy.RUNTIME)
public @interface StateValidate {   
    String message() default "Invalid State";
    Class<?>[] groups() default {};
    Class<? extends Payload>[] payload() default {};
}


package com.example.demo;

import javax.servlet.http.HttpServletRequest;
import javax.validation.ConstraintValidator;
import javax.validation.ConstraintValidatorContext;

import org.springframework.beans.factory.annotation.Autowired;

public class StateValidator implements ConstraintValidator<StateValidate, String>{

    @Autowired
    private HttpServletRequest httpServletRequest;

    @Override
    public boolean isValid(String value, ConstraintValidatorContext context) {
        //TODO you can check code size as per requirement
        }        
    }
}

You need to annotate @StateValidate at any field you looking for

This will be more controlled approach and if needed i18 can be used to manage to support multiple countries.

Yes POJO can be same... these are different validation rules you are creating on condition — Swarit Agarwal, Feb 12 '20 at 06:42
This is a kind of custom validation with cross fields, perhaps I have to write same kind of validation rule , is there any other way to reuse the annotation based on parameter. — Vasanth, Feb 13 '20 at 04:20
You might enhance it with **Generics**, I would be a great experiment to do — Swarit Agarwal, Feb 13 '20 at 04:21

score 0 · Answer 2 · answered Feb 16 '20 at 21:48

I got reference from given below links.
stackover flow .
Programmatic constraint definition

 HibernateValidatorConfiguration configuration = Validation.byProvider(HibernateValidator.class).configure();   
             ConstraintMapping constraintMapping = configuration.createConstraintMapping();
 if(geoLocation.getType().equals("AUS")) {
                 constraintMapping
                 .type(GeoLocation.class)
                 .property("cityName", ElementType.FIELD)
                 .constraint(new NotNullDef().message("cityName should not empty")) 
                 .constraint(new SizeDef().min(3).message("Minimum 3 charater"))
                 .constraint(new SizeDef().max(50).message("Maximum 50 character"));
                 }else if(geoLocation.getType().equals("IND")) {
                     constraintMapping
                     .type(GeoLocation.class)
                     .property("cityName", ElementType.FIELD)
                     .constraint(new NotNullDef().message("cityName should not empty"))                
                     .constraint(new SizeDef().min(10).message("Minimum 10 charater"))
                     .constraint(new SizeDef().max(15).message("Maximum 15 character"));

                 }


             validator=configuration.addMapping(constraintMapping).buildValidatorFactory().getValidator();
             resultSet= validator.validate(geoLocation);
             for (ConstraintViolation<Object> object : resultSet) {
               System.out.println(object.getPropertyPath() + ": " + object.getMessage());
           }

Different validation annotation rule for same Data Access Object

2 Answers2