Validating properties that are not yet set

papegaaij · **Joined:** Fri May 29, 2009 4:02 am **Posts:** 4

In the Apache Wicket framework, validation is performed before any of the properties are set on the object. When a validation error occurs, the properties are not set at all. With the current API available, validation in Wicket would be limited to using the Validator.validateValue, which can only validate constraints on properties. Is it perhaps possible to add a method to the Validator interface that accepts a set of 'properties-to-be-set'? Something like:

Code:

<T> Set<ConstraintViolation<T>> validate(T object, Map<String, Object> properties, Class<?>... groups);
or
<T> Set<ConstraintViolation<T>> validate(T object, Set<PropertyValue> properties, Class<?>... groups);

Another option would be to provide the posibillity for using a custom PropertyResolver, which would allow property values to be taken from a different source (not the object being validated), such as a map.

Best regards,
Emond Papegaaij

emmanuel · **Posted:** Mon Jun 22, 2009 1:51 pm

this idea has been floating around but we could not come up with a satisfying API. That's something I hope providers will address and that will be standardized in the next part of the spec if needed.

papegaaij · **Joined:** Fri May 29, 2009 4:02 am **Posts:** 4

How are these providers going to work? I couldn't find anything about it in the current version of the spec.

emmanuel · **Posted:** Fri Jul 03, 2009 12:27 pm

Code:

validator.unwrap(HibernateValidator.class).validateProperty(superdupperAPIHere);

check out http://people.redhat.com/~ebernard/validation/