hibernate-validator

Details: I am making form-validation using javax-validation and hibaernate-validator in Spring. Other than basic necessary JAR files for Spring. I have included: validation-api-1.1.0.Final hibernate-validator-5.1.0.Final I read somewhere that spl4j version is also in concern: so I'm also telling: ###slf4j-api-1.7.5### ###slf4j-simple-1.7.5### ###log4j-1.2.17### Can the cause of error be due to slf4j and log4j compatibility? I use annotation base validation. Let me provide some code: Customer.java import java.util.Date; import javax.validation.constraints.Max; import javax.validation

In my controller I have a method for creating an entity import javax.validation.Valid; ... @RestController public class Controller { @RequestMapping(method = RequestMethod.POST) public ResponseEntity<?> create(@Valid @RequestBody RequestDTO requestDTO) { ... with import org.hibernate.validator.constraints.NotEmpty; ... public class RequestDTO @NotEmpty // (1) private String field1; //other fields, getters and setters. I want to add a controller method update(@Valid @RequestBody RequestDTO requestDTO) but in this method it should be allowed for field1 to be empty or null, i.e. the line

I'm using hibernate-validator 4.3.1 and Spring MVC 3.2.3. My application has a bean with the following properties and annotations (I've removed most of them to make it simple): public class Account { @NotEmpty(groups = GroupOne.class) private String name; @NotEmpty(groups = GroupOne.class) private Date creationDate; @NotEmpty(groups = GroupTwo.class) private String role; @NotEmpty(groups = GroupTwo.class) private String profile; //getters and setters } As it is showed, there are two groups of validations because the application has a wizard-form composed of two steps: in the first step the

I will try to ignore other details and make it short: @Entity public class User @UniqueEmail @Column(unique = true) private String email; } @Component public class UniqueEmailValidatior implements ConstraintValidator<UniqueEmail,String>, InitializingBean { @Autowired private UserService userService; @Override public void initialize(UniqueEmail constraintAnnotation) { } @Override public boolean isValid(String value, ConstraintValidatorContext context) { if(userService == null) throw new IllegalStateException(); if(value == null) return false; return !userService.isEmailExisted(value); } } This

I'm trying to do some spring validation with the error messages in properties files. But the examples I find all seem to have the values hardcoded, or gotten from a properties file but using a validator class and retrieving it there. My setup is a bit different. I'm using the @Valid annotation in my requestmapping, and my @Valid class uses @NotNull etc. I've seen some examples where people do @NotNull(message = "blablabla"); But that's also hardcoded, and I'd like to put the messages in a properties file so I can easily edit it on the fly and so I can easily implement i18n in the future. Any

I've configured a JSR-303 custom validator following what's given in the docs ( http://docs.spring.io/spring/docs/4.0.x/spring-framework-reference/html/validation.html ), complete with LocalValidatorFactoryBean and Hibernate validator on the classpath. However, my validator just refuses to kick in. I've put up a dirt simple test project here ( https://github.com/abhijitsarkar/java/tree/master/spring-jsr-303 ), along with a failing unit test. Should you decide to take a look, just clone it and run gradlew clean test from the root directory. I'm using Spring framework 4.0.2.RELEASE and Hibernate

i have a field that have two validation annotations @NotEmpty @Length(min=3,max=100) String firstName; i am just curious to know how hibernate is specifying the order of which validation annotation to be executed first, and if it's possible to custom that ? the reason i am asking is that if i left that field empty sometimes the first validation message displayed is for not empty and other times if i left it empty i get the validation message for the length annotation. thanks in advance. Use JSR-303 validation groups. If no groups are specified a constraint is part of the Default Bean