Hi again,
Back to this issue, the commits to branch 2.0 of the TCK are fine.
However, as I continue working through our list of TCK failures, I
managed to trigger another problem with this same composed constraint.
It is explicitly applied to RETURN_VALUE of Person.getAge(), but the
@CustomComposingConstraint is applied to PARAMETERS, which by my
current cut of code runs afoul of the requirement in section 3.1.1.4
that it is illegal to specify PARAMETERS on an executable with no
parameters.
Matt
On Mon, Mar 26, 2018 at 4:07 AM, Guillaume Smet
<guillaume.smet(a)gmail.com> wrote:
Hi Matt,
On Fri, Mar 23, 2018 at 6:46 PM, Matt Benson <mbenson(a)apache.org> wrote:
>
> I therefore conclude that the constraint applied to Person#getAge() is
> incorrectly composed.
So do I:
https://hibernate.atlassian.net/browse/BVTCK-199
https://github.com/beanvalidation/beanvalidation-tck/pull/162
Cheers,
--
Guillaume
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev