Define method that must validate to true and put the @AssertTrue annotation on the top of it: @AssertTrue private boolean isOk() { return someField != something || otherField != null; } The method must start with ‘is’.
I created simple class: public class Mock { @Size(min=1, max=3) private List<String> strings; public List<String> getStrings() { return strings; } public void set(List<String> strings) { this.strings = strings; } } And test: Mock mock = new Mock(); mock.setStrings(Collections.emptyList()); final Set<ConstraintViolation<Mock>> violations1 = Validation.buildDefaultValidatorFactory().getValidator().validate(mock); assertFalse(violations1.isEmpty()); mock.setStrings(Arrays.asList(“A”, “B”, “C”, “D”)); final Set<ConstraintViolation<Mock>> violations2 = Validation.buildDefaultValidatorFactory().getValidator().validate(mock); assertFalse(violations2.isEmpty()); It … Read more
There are 2 compliant implementations now: Apache Bean Validation (formerly agimatec) Hibernate Validator You can access a benchmark and a quick description of both here: http://carinae.net/2010/06/benchmarking-hibernate-validator-and-apache-beanvalidation-the-two-jsr-303-implementations/
I would suggest that you look at Spring JS, which relies heavily on Dojo. A tutorial can be found here. Easiest way for yourself to start playing with it is to download Spring Roo, create the petclinic sample application with one of the example-scripts (this takes you 5 minutes) and then play around with how … Read more
As [M. Deinum] mentioned in a comment on my original post, the solution is to set: spring.jpa.properties.javax.persistence.validation.mode=none In the application.properties file. Additionally, this behaviour is described here (its easy to miss because no example is provided).
Yes, just add @Valid to the collection. Here is an example from the Hibernate Validator Reference. public class Car { @NotNull @Valid private List<Person> passengers = new ArrayList<Person>(); } This is standard JSR-303 behavior. See Section 3.1.3 of the spec.
You need to use Annotation use-site targets since the default for a property declared in the constructor is to target the annotation on the constructor parameter instead of the getter (which will be seen by JavaBeans compliant hosts) when there are multiple options available. Also using a data class might be inappropriate here (see note … Read more
For JSR-303 bean validation to work in Spring, you need several things: MVC namespace configuration for annotations: <mvc:annotation-driven /> The JSR-303 spec JAR: validation-api-1.0.0.GA.jar (looks like you already have that) An implementation of the spec, such as Hibernate Validation, which appears to be the most commonly used example: hibernate-validator-4.1.0.Final.jar In the bean to be validated, … Read more
For multiple properties validation, you should use class-level constraints. From Bean Validation Sneak Peek part II: custom constraints: Class-level constraints Some of you have expressed concerns about the ability to apply a constraint spanning multiple properties, or to express constraint which depend on several properties. The classical example is address validation. Addresses have intricate rules: … Read more
@NotNull: The CharSequence, Collection, Map or Array object is not null, but can be empty. @NotEmpty: The CharSequence, Collection, Map or Array object is not null and size > 0. @NotBlank: The string is not null and the trimmed length is greater than zero. To help you understand, let’s look into how these constraints are … Read more