[bv-dev] Triggering method validation

Emmanuel Bernard emmanuel at hibernate.org
Tue Jan 31 03:21:29 EST 2012


I'm not sure. As I said, constructors and methods are likely to be intercepted much differently so a isMethodConstrained won't cut it. 

What we can do is a `isConstrained(ConstrainType... type)` where ConstrainType is an enum. But I'd like to refine the use case before adding such method. 

On 30 janv. 2012, at 18:43, Gunnar Morling <gunnar.morling at googlemail.com> wrote:

> That's a good point.
> 
> The proposal currently suggests to redefine BeanDescriptor#isConstrained() to let it return true also if there are any method level constraints. Another idea would be to leave it as is and add another method such as isMethodConstrained(), slightly simplifying your use case.
> 
> I think I actually would like that better. WDYT?
> Am 30.01.2012 09:47 schrieb "Emmanuel Bernard" <emmanuel at hibernate.org>:
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/beanvalidation-dev/attachments/20120131/82166dbd/attachment.html 


More information about the beanvalidation-dev mailing list