Consider higher level validations, such as email, URL, credit card, etc. ------------------------------------------------------------------------ Key: ANN-150 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-150 Project: Hibernate Annotations Issue Type: New Feature Components: validator Affects Versions: 3.1beta6 Reporter: Ted Bergeron Priority: Minor I was looking at the release notes for commons validator 1.2 http://wiki.apache.org/jakarta-commons/ValidatorVersion120 and wondered if the higher level constructs fit the design goals of hibernate validator. They have email, URL, Credit card and ISBN. These could all be handled via @Pattern with regex matching a constant declared somewhere. Would it be desirable to have Hibernate supply the values for these constants? Such as: @Pattern(type="email") or @Pattern(regex=org.hibernate.validator.Pattern.EMAIL) or @Email Email and URL are global patterns. This probably wouldn't work for something like phone number which is locale sensitive.