<div dir="ltr"><div>Hi all,</div><div><br></div>Consider InvalidGroupConversionInPropertyLevelOverridingTest#testGroupConversionsAreAdditiveAndExceptionIsThrownForMultipleConversionWithSameSource():<div><br></div><div>This test purports to enforce that a ValidationException is thrown because a property
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">specifies<span> </span></span>
multiple group conversions from the Default group. However, the example actually specifies one via the annotated getter, and the other via the XML-configured field. I can't find that the spec is perfectly clear on this, but it is clear that a property should be accessed using the mechanism of constraint declaration. I don't recall where, but the TCK tests proper validation of field vs. getter even when the objects returned are different. I would therefore argue that there could be some legitimate reason to apply a different group conversion to field vs. getter, and that the test case should be changed to specify the XML constraint via getter as does the User class definition overridden.<br><div><br></div><div>Matt</div></div></div>