Gunnar wrote:

Emmanuel, what was our intention when forbidding to specify @Valid several times? Forbidding several occurrences of @ConvertGroup makes sense to me due to the LSP, but several @Valid don't seem problematic to me.

Or was it to "transitively" cover the @ConvertGroup case since we also say
that @ConvertGroup may only be given where @Valid is specified?

I think it would make sense to either

• Forbid several occurrences of @Valid (subtypes, parallel hierarchies); Allow @ConvertGroup only where @Valid is given; Don't have additional rules for @ConvertGroup

OR

• Allow several occurrences of @Valid; Allow @ConvertGroup only where
  @Valid is given; Forbid several occurrences of @ConvertGroup (subtypes, parallel hierarchies)

Mailing list: http://lists.jboss.org/pipermail/beanvalidation-dev/2013-January/000789.html