I was wondering if and how an annotation with invalid data should be handled, for example

@Length(min=10, max=4)

Currently, Contstraint isn't defined to let any checked exceptions be thrown. Which of the following are appropriate response(s) for a Constraint implementation in this case?

1. RuntimeException in initialize(...)
2. RuntimeException in isValid(...)
3. isValid always returns false, placing a message in the ConstraintContext indicating the constraint is impossible to meet.
4. isValid always returns false without any indication that the constraint is not possible to meet
5. possible spec change to allow something like an InvalidConstraintException to be thrown by initialize(...)

0. replace @Length with @Min @Max as it prevents the trap :)
and 1. is what I had in mind. i need to write up the exception part of the spec.

Started to review and test the current implementations of the builtin constraints and wonder the same thing.
Created a Jira issue for it: http://opensource.atlassian.com/project ... e/BVAL-117