hi @ all,<div><br></div><div>@ &quot;treat getter-methods as regular methods for method-validation&quot;:</div><div><div>there are cases which would benefit from it, but such a behaviour can also break a lot!</div><div><br>

</div><div>-&gt; if we support it:</div><div>imo we need a global config option as well as an api for de-/activating it. in case of the api we would also need a possibility for de-/activating it dynamically for one validation process. e.g. in a jsf application there is only one phase (invoke application) of the request-lifecycle for which such a feature could make sense (and for a lot of applications not even there). in all other phases it just doesn&#39;t make sense and it would just be a performance penalty which only leads to side-effects you can hardly control (if a jsf implementation doesn&#39;t handle it explicitly).</div>

</div><div><br></div><div>that&#39;s imo also true for many other constellations which are independent of jsf.</div><div><br></div><div>regards,</div><div>gerhard<br><br><br><br><div class="gmail_quote">2012/11/9 Hardy Ferentschik <span dir="ltr">&lt;<a href="mailto:hardy@hibernate.org" target="_blank">hardy@hibernate.org</a>&gt;</span><br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have to back up Gunnar on this one on all counts :-)<br>
<div class="im"><br>
On 9 Jan 2012, at 10:13 AM, Gunnar Morling wrote:<br>
<br>
&gt; Generally I don&#39;t think that considering getters during method validation really is a problem. So I wouldn&#39;t really have a problem with this being the default behavior (which it also is in the proprietary API in HV 4.3). I&#39;d prefer that over excluding certain named methods from method validation as this goes against the principle of least surprise and would feel like an inconsistency to me.<br>


<br>
</div>+1<br>
<div class="im"><br>
&gt; But if validating getters during method validation really is a problem, I&#39;d expect this to be the case generally throughout an application or system. Taking the example of JPA entities which used to be validated upon persisting only and now would their property constraints get validated upon getter invocation, then I&#39;d prefer to disable getter validation globally instead of marking each individual property with an annotation.<br>


<br>
</div>+1<br>
<div class="im"><br>
&gt; If I as a user really needed a configuration per element, I could do so using validation groups. If for instance single constraints should not be validated upon getter invocation, I could use a group like this:<br>
<br>
</div>+1<br>
<br>
Are not more people have an opinion on this issue?<br>
<div class="HOEnZb"><div class="h5"><br>
--Hardy<br>
_______________________________________________<br>
beanvalidation-dev mailing list<br>
<a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
</div></div></blockquote></div><br></div>