I was reading http://in.relation.to/Bloggers/BeanVali ... onstraints and it says
"As you can see the interface entirely focuses on validation and leaves other concerns such as error rendering to the bean validation provider."
which seem the right thing to do.

My query was with rendering specific error messages when an object isn't valid using a class validator.

Taking the Address class validator as an example. Say the country code was FR and the zip was invalid, and we want the error message to say "Invalid zip code for France".

It would seem then that the validation renderer would need to also have the zip/country service and run the same validation logic again when processing an InvalidConstraint to determine the appropriate error message.

I know if we rewrote our current validations on my project then we would have this situation. Other than that it looks good!

dan

The message aspect needs to be revisited. sounds like we might have to add some ValidationContext object in isValid() to deal with such cases :(