If you can, can you dive a bit into the specific example you are facing? Which state
business wise would be useful to decide of the group? The Hibernate Validator mentions
security levels. I wanted to see more use cases to get a better feeling before committing
to a feature.
Emmanuel
On 28 Jan 2015, at 05:06, kabooom <kabooom(a)op.pl> wrote:
Use cases are the same as described in Hibernate Validator documentation:
http://docs.jboss.org/hibernate/validator/5.1/reference/en-US/html_single...
"(...) dynamic redefinition of default group sequences depending on the object
state".
It would allow to validate appriopriate (dependent on bean's state) Groups on
automatically trigerred validation, however I just realized that I could probably
workaround this performing validation in class specified in @EntityListeners list, so now
I am not sure is GroupSequenceProvider necessary.
Peter
W dniu 2015-01-27 08:17:02 użytkownik Emmanuel Bernard <emmanuel(a)hibernate.org>
napisał:
> Hi Peter,
>
> Could you give us the use cases in which you would make use of this feature? It helps
to make choices and improve the feature further when possible.
>
> Emmanuel
>
>> On 25 Jan 2015, at 22:08, kabooom <kabooom(a)op.pl> wrote:
>>
>> Hi,
>> It would be great to have GroupSequenceProvider - which is already implemented in
Hibernate Validator- also in Bean Validation specification.
>> Thank you.
>> Peter
>> _______________________________________________
>> beanvalidation-dev mailing list
>> beanvalidation-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
>
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev