[hibernate-issues] [Hibernate-JIRA] Updated: (HV-20) Include the Validator class on the InvalidValue object

[Hardy Ferentschik (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HV-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hardy Ferentschik updated HV-20:
--------------------------------

    Component/s:     (was: engine)
                 legacy

Moved issue into legacy component. This issue applies to codebase prior 4.x

> Include the Validator class on the InvalidValue object
> ------------------------------------------------------
>
>                 Key: HV-20
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-20
>             Project: Hibernate Validator
>          Issue Type: Improvement
>          Components: legacy
>            Reporter: Leonardo Quijano
>            Priority: Minor
>
> It'd be nice to know which validator caused an InvalidValue entry to appear.
> For example, for a @NotNull annotation we'd have:
> InvalidValue.getValidatorClass() == org.hibernate.validator.NotNullValidator
> Then, on the web layer of the application, we could iterate over every InvalidValue[], summarizing all the NotNullValidator entries we get, and showing a msg:
> * Some required fields are missing.
> (and put some asterisks on the required fields, for example).
> (I guess that can be done with an additional BeanValidator, but this solution lets us work with the InvalidValue[] array after all validation has taken place)

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