<div dir="ltr">My vote is for #hasConstrainedParameters().<div><br></div><div style>Thanks,</div><div style>Matt</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 28, 2013 at 7:59 AM, Rich Midwinter <span dir="ltr"><<a href="mailto:rich.midwinter@gmail.com" target="_blank">rich.midwinter@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Perhaps worth mentioning we have BeanDescriptor#isBeanConstrained() too in 1.0. So at first glance I'd probably suggest isParameterConstrained() and also isExecutableConstrained().<span class="HOEnZb"><font color="#888888"><br>
<br>Rich</font></span><div class="HOEnZb"><div class="h5"><br><br>On Thursday, 28 February 2013, Gunnar Morling <<a href="mailto:gunnar@hibernate.org" target="_blank">gunnar@hibernate.org</a>> wrote:<br>
> Hi all,<br>> Hardy and I were wondering whether the method name ExecutableDescriptor#areParametersConstrained() is the best choice.<br>> The name seems a bit unintuitive, when e.g. looking via auto-completion for boolean getter methods which typically start with "is" or "has". Maybe <br>
> * "isParameterConstrained()" (as in "is constrained on at least one parameter") or <br>> * "hasConstrainedParameters()" would be better alternatives?<br>><br>> The latter would also nicely match with BeanDescriptor#hasConstrainedExecutables().<br>
> WDYT?<br>> --Gunnar<br>>
</div></div><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></blockquote></div><br></div>