[
http://opensource.atlassian.com/projects/hibernate/browse/HV-70?page=com....
]
Emmanuel Bernard commented on HV-70:
------------------------------------
As a class-level constraint yes but I am more in favor of letting users write their own.
@SamePassword(old, new) is more meaningful than @Equals(property1, property2)
Add @Equals(property="name")
----------------------------
Key: HV-70
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-70
Project: Hibernate Validator
Issue Type: New Feature
Affects Versions: 3.1.0.CR2
Reporter: Juergen Zimmermann
It would be nice to have something like:
public class Customer implements Serializable {
private String password;
@Equals(property="password") // the name of the property above
private String password2;
...
}
Such entity classes would be helpful for user interfaces e.g. inside registration pages
where you want to avoid typos or ensure that a human being is registering.
--
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