[hibernate-issues] [Hibernate-JIRA] Commented: (HV-70) Add @Equals(property="name")

[David Parks (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HV-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39059#action_39059 ] 

David Parks commented on HV-70:
-------------------------------

Here is an excellent implementation. I would recommend contacting this guy and using his implementation.

And to vote for this: as a new user I ran into this missing-feature day one and it really made me wonder how complete the package is. This seems like pretty simple functionality that the average user shouldn't be writing custom annotations to implement. Who doesn't need to validate that two passwords are the same? That's common to virtually every app right?

http://stackoverflow.com/questions/1972933/cross-field-validation-with-hibernate-validator-jsr-303


> Add @Equals(property="name")
> ----------------------------
>
>                 Key: HV-70
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-70
>             Project: Hibernate Validator
>          Issue Type: New Feature
>          Components: legacy
>    Affects Versions: 3.1.0.CR2
>            Reporter: Juergen Zimmermann
>             Fix For: 3.2.0
>
>
> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira