[hibernate-issues] [Hibernate-JIRA] Created: (HV-170) Refactor the group sequence expansion and take the default sequence expansion of the validated entity into considertation

Refactor the group sequence expansion and take the default sequence expansion of the validated entity into considertation ------------------------------------------------------------------------------------------------------------------------- Key: HV-170 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-170 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.Beta2 At the moment the group sequence expansion does not take into consideration any default group re-definition of the validated entity. However, it should epbernard: say I have Complete -> Default, Heavy that's a regular sequence epbernard: then on class A, I have @GS(Heavy, A) epbernard: When expanding I have Heavy, A, Heavy => exception hardy: epbernard: so you mean validator( aEntity, Complete.class) epbernard: We have Default before Heavy epbernard: and Default is defined as Heavy before A epbernard: To the sequence is Heavy A Heavy epbernard: ah hold on let me think hardy: right hardy: so we actually really HAVE to pass the entity to the GroupChainGenerator epbernard: ah yes so let's assume that < means before ok? epbernard: hardy: sebersole: why dont you guiys get a room? epbernard: Default < Heavy means Heavy < Heavy (accepted by the spec) and A < Heavy epbernard: but we also have Heavy < A (the defainintion of Default) epbernard: hence the inconsistency -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira