[bv-dev] TCK expects tolerance of mismatched constraint and constraint validator

Matt Benson mbenson at apache.org
Fri Mar 16 15:18:08 EDT 2018

Similarly, ZeroConstraintValidator is declared as targeting @Negative.

On Mar 16, 2018 1:44 PM, "Matt Benson" <mbenson at apache.org> wrote:

> On Mar 16, 2018 1:39 PM, "Matt Benson" <mbenson at apache.org> wrote:
> FrenchAddressListContainer defines @FrenchZipcodeListContainer as a
> constraint that is validated by FrenchZipcodeConstraintValidator, but
> that class declares its constraint type parameter as @FrenchZipCode.
> Same for FrenchZipcodeMixDirectAnnotationAndListContainer.
> Because
> that CV type does not override #init() this presumably works in the RI,
> and the spec is a bit vague on this point, but the interface definition
> describes type parameter A as "the annotation type handled by an
> implementation." The spec section ConstraintValidator resolution algorithm
> also correlates constraint A to the type parameters of the
> ConstraintValidators described in the resolution rules. Finally, I don't
> see anything under "What's new in 2.0" to indicate that this should be a
> legal constraint definition.
> Can I get a ruling? :)
> Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/beanvalidation-dev/attachments/20180316/2ef22071/attachment-0001.html 

More information about the beanvalidation-dev mailing list