[hibernate-issues] [Hibernate-JIRA] Commented: (ANN-150) Consider higher level validations, such as email, URL, credit card, etc.

[Diego Pires Plentz (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_26710 ] 

Diego Pires Plentz commented on ANN-150:
----------------------------------------

We already have @Email and @CreditCardNumber. Do you think that makes sense to add @ISBN and @URL to Validator?

> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira