[hibernate-issues] [Hibernate-JIRA] Resolved: (HV-86) <T> in ValidatorContext<T> Validator<T> and InvalidConstraint<T> are inadequately considered unique
Hardy Ferentschik (JIRA)
noreply at atlassian.com
Fri Jun 26 04:58:34 EDT 2009
[ http://opensource.atlassian.com/projects/hibernate/browse/HV-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hardy Ferentschik resolved HV-86.
---------------------------------
Resolution: Fixed
Got resolved as part of the refactorings for HV-177
> <T> in ValidatorContext<T> Validator<T> and InvalidConstraint<T> are inadequately considered unique
> ---------------------------------------------------------------------------------------------------
>
> Key: HV-86
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-86
> Project: Hibernate Validator
> Issue Type: Sub-task
> Components: engine
> Reporter: Emmanuel Bernard
> Assignee: Hardy Ferentschik
>
> In ValidatorImpl.validate()
> T Generic of ValidatorContext<T> and InvalidConstraint<T> are likely to be different than the Validator<T>
> A context can be created in a validator (T are equal). but the same context (a clone really) can be passed to a sub validator. Ts are then different. I believe it's the same for InvalidConstraints. An IC created by a subvalidator<U> will craete IC<U>, you will need to convert them in IC<T> when coming to the root validator<T>.
> So we need something like
> private <U> List<InvalidConstraintImpl<T>> validate(ValidationContext<U> context, List<String> groups) { }
> same for similar methods.
--
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
More information about the hibernate-issues
mailing list