[
https://issues.apache.org/jira/browse/BVAL-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456608#comment-13456608
]
Matt Benson commented on BVAL-109:
----------------------------------
My original comment explained why I believe the request violates the letter of
the specification: Groups are explained in the spec under the subheading
{{Group and group sequence}} (section 3.4 in the 1.0 spec, section 4.4 in the
current 1.1 draft [1]), where the direct quote, again, is "Groups are
represented by interfaces." The statement is in a paragraph by itself,
impossible to miss and seemingly quite direct in its intent.
Once again, I am completely amenable to the possibility of enabling this
behavior with a property.
1.
http://beanvalidation.org/latest-draft/spec/#constraintdeclarationvalidationprocess-groupsequence
> Wrong enforcement that validation groups have to be interfaces
> --------------------------------------------------------------
>
> Key: BVAL-109
> URL: https://issues.apache.org/jira/browse/BVAL-109
> Project: BVal
> Issue Type: New Feature
> Components: jsr303
> Affects Versions: 0.4
> Reporter: Konstantin Triger
> Fix For: 0.5
>
>
> The Bean Validation specification does not enforce that groups have to be
> interfaces. Non interface classes could be used as well, but we recommend to
> stick to interfaces.
> (Taken from
> http://docs.jboss.org/hibernate/validator/4.0.1/reference/en/html/validator-usingvalidator.html#validator-usingvalidator-validationgroups)
> Suggested fix: remove the check from GroupsComputer.computeGroups.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
