<div dir="auto"><div><div class="gmail_extra"><div class="gmail_quote">On Mar 16, 2018 1:39 PM, "Matt Benson" <<a href="mailto:mbenson@apache.org">mbenson@apache.org</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">FrenchAddressListContainer defines @FrenchZipcodeListContainer as a constraint that is validated by FrenchZipcodeConstraintValidat<wbr>or, but that class declares its constraint type parameter as @FrenchZipCode. </div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">Same for FrenchZipcodeMixDirectAnnotationAndListContainer.</div><div dir="auto"><br></div><div dir="auto">Because</div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"> 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.<div dir="auto"><br></div><div dir="auto">Can I get a ruling? :)</div><font color="#888888"><div dir="auto"><br></div><div dir="auto">Matt</div></font></div>
</blockquote></div><br></div></div></div>