[hibernate-issues] [Hibernate-JIRA] Resolved: (BVAL-59) Rethink the group sequence inheritance rules

[Emmanuel Bernard (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/BVAL-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bernard resolved BVAL-59.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0 public draft

> Rethink the group sequence inheritance rules
> --------------------------------------------
>
>                 Key: BVAL-59
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-59
>             Project: Bean Validation
>          Issue Type: Improvement
>          Components: spec-general
>            Reporter: Emmanuel Bernard
>             Fix For: 1.0 public draft
>
>
> Sebastian wrote:
> 3-F) 3.4 "Two group sequences must not share the same group name in a
> given object graph". Does this mean If an object of type A references an
> object of type B and A and B have a group sequences with the same name
> this would result to an exception? Why would such a limitation be
> necessary? Or is the term "object graph" misplaced here?
> Emmanuel replied:
> "When an object graph is validated (through the use of @Valid), the children elements of the graph inherit the sequence definitions of their parent."
> Yes this was the intend. Because group sequence definitions are inherited from a parent to a child, the rule makes sense.
> I think you assumed that a group sequence was not inherited. Children would be validated against the expanded groups of their parents.
> Let's go back to the drawing board (in a different thread) and evaluate the merit of both rules using common usecases.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira