[
http://opensource.atlassian.com/projects/hibernate/browse/HV-19?page=com....
]
Diego Pires Plentz commented on HV-19:
--------------------------------------
Detect the protocol http / mailto etc, then you can refine the regexp
accordingly. Typically mailto can delegate to the EmailValidator
But an email isn't a valid url type, right? So, if someone enter an email instead of
an url, we can't accept as a valid url.
Consider higher level validations, such as email, URL, credit card,
etc.
------------------------------------------------------------------------
Key: HV-19
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-19
Project: Hibernate Validator
Issue Type: New Feature
Components: validators
Reporter: Ted Bergeron
Assignee: Diego Pires Plentz
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira