<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 27 août 2012, at 10:51, Gunnar Morling wrote:</div><blockquote type="cite"><p>For the “getter“ approach, getMethodValidator() would be defined on ValidatorFactory, right? At least that was the original idea.</p></blockquote><br></div><div>Ah. I was thinking `getMethodValidator()` was hosted to `Validator`. The negative I could see are:</div><div><br></div><div>1. `ValidatorContext` needs to be updated too</div><div>2. we would require to allow injection of `MethodValidator` in injectable environments</div><div>3. we will need to duplicate `getConstraintsForClass` and `unwrap` in `MethodValidator`</div><div><br></div><div>Independently, they don't weight much (except point 3) but as a whole I wonder if that's the right approach.</div><div>What would be the negative points of putting it on `Validator`? It requires one extra method call. Any other?</div><div><br></div><div>Emmanuel</div><br></body></html>