<div dir="ltr"><div class="gmail_extra">2013/1/21 Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div id=":54a">My concern around the latest option is that it forces us to be a<br>
subclass of ConstraintViolation for the foreseeable future including<br>
when we reopen the type-safe options we explored in<br>
<a href="http://beanvalidation.org/proposals/BVAL-232/" target="_blank">http://beanvalidation.org/proposals/BVAL-232/</a></div></blockquote><div><br></div><div style>If we want to include a type-safe approach later on, we might do it like this:</div>
<div style><br></div><div style>* Pull ConstraintValidator#initialize() up into a new interface Initializeable</div><div style>* Change @CrossParameterConstraint#validatedBy() to return Class<? <span class="">extends</span> Initializable<?, ?>>. AFAICS that shouldn't be a problem for existing constraint definitions, BV providers need of course to adapt. Short tests I did looked good.</div>
<div style><br></div><div style>--Gunnar<br></div></div></div></div>