[bv-dev] Ordered Validation (practically)

[Emmanuel Bernard]

I have created https://hibernate.onjira.com/browse/BVAL-259

On 4 janv. 2012, at 16:39, Peter Davis wrote:

> The order I'm suggesting is child<parent which is perfectly well defined.  With @ReportAsSingleViolation the result (the ConstraintViolation) is identical no matter which child validation fails, so why invoke the parent's validator?
> 
> Regards,
> Peter Davis
> 
> On Jan 3, 2012, at 23:55, Gunnar Morling <gunnar.morling at googlemail.com> wrote:
> 
>> Hi,
>> 
>> welcome to the list.
>> 
>> > "When @ReportAsSingleViolation is present, short circuit."
>> 
>> I think the problem here is that this approach relies on the order of constraint annotations as specified in the source code. AFAIK there is no way to retrieve annotations which would garuantee this order.
>> 
>> Another question would be how constraints from different sources (annotation, XML) would be ordered.
>> 
>> --Gunnar
>> 
>> Am 04.01.2012 07:37 schrieb "Peter Davis" <davispw at gmail.com>:
>> _______________________________________________
>> beanvalidation-dev mailing list
>> beanvalidation-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
> _______________________________________________
> 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/20120105/20100c9c/attachment.html