Ah. I was reading isParameterConstrained as the singular executable
constrained by parameters… which makes a lot less sense now than it seemed
to earlier! Another one in favour of hasConstrainedParameters() then.
On Thursday, 28 February 2013, Emmanuel Bernard <emmanuel(a)hibernate.org>
hasConstrainedParameters() is better that the current situation.
But then we also need to move to hasConstrainedReturnValue().
Rich, we could not find a use case for ExecutableDescriptor hosting
isExecutableConstrained() and the singular isParameterConstrained does
not work here as we are looking at the method aggregating all params
for a given executable.
On Thu 2013-02-28 10:06, Matt Benson wrote:
> My vote is for #hasConstrainedParameters().
> On Thu, Feb 28, 2013 at 7:59 AM, Rich Midwinter <rich.midwinter(a)gmail.com
> > Perhaps worth mentioning we have BeanDescriptor#isBeanConstrained()
> > 1.0. So at first glance I'd probably suggest
> > also isExecutableConstrained().
> > Rich
> > On Thursday, 28 February 2013, Gunnar Morling <gunnar(a)hibernate.org>
> > wrote:
> > > Hi all,
> > > Hardy and I were wondering whether the method
> > name ExecutableDescriptor#areParametersConstrained() is the best
> > > The name seems a bit unintuitive, when e.g. looking via
> > for boolean getter methods which typically start with
"is" or "has".
> > > * "isParameterConstrained()" (as in "is
constrained on at least one
> > parameter") or
> > > * "hasConstrainedParameters()" would be better alternatives?
> > >
> > > The latter would also nicely match with
> > BeanDescriptor#hasConstrainedExecutables().
> > > WDYT?
> > > --Gunnar
> > >
> > _______________________________________________
> > beanvalidation-dev mailing list
> > beanvalidation-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
> beanvalidation-dev mailing list
beanvalidation-dev mailing list