|
Description:
|
Gunnar wrote
In section 4.5.5 we say
:
{quote}
Emmanuel
One must not mark a method return value for cascaded validation more than once in a class hierarchy. In other words
,
what was our intention when forbidding to specify {{@Valid}} several times? Forbidding several occurrences of {{@ConvertGroup}} makes sense to me due to
sub types (be it sub classes/interfaces or interface implementations) cannot mark
the
LSP, but several
return value for cascaded validation if the return value has already been marked on a super type or interface.
{
{@Valid
quote
}
} don't seem problematic to me.
Or was it
It would be good IMO
to
clarify what
"
transitively
class hierarchy
"
cover the {{@ConvertGroup}} case since we also say
means, i.e.
that
{{@ConvertGroup}} may only be given where {{@Valid}} is specified?
I think
it
would make sense
is ok
to
either
* Forbid several occurrences of {{
specify
@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,
times in
parallel
hierarchies)
{quote}
Mailing list: http://lists
types
.
jboss.org/pipermail/beanvalidation-dev/2013-January/000789.html
|
