[epbernard]

Sorry I was refering the initial syntax

[gnulp]

nevertheless you are right - I firstly also thought we can put it into the HibernateValidator - but that is wrong ! Hibernate has no idea about the @IfInvalid-annotation - thus it can not be handled there ...

Thats why I added a separate SeamClassValidator that is managing the combined validation ...

It would be great if hibernate ClassValidator is adapted in a way that derivative implementation is possible so we need not to copy every change here and there !!! Currently I had no chance because of private-security in hibernates ClassValidator and there are no setters nor getters (protected for the most variables and methods would be perfect ;-) ...

[epbernard]

Your patch mix and match Seam and Validator notions.
But it is doable to filter the validation mechanism by passing a list of specific path to test.

[gnulp]

Your patch mix and match Seam and Validator notions.

I don't understand what you mean ...

But it is doable to filter the validation mechanism by passing a list of specific path to test.

Does it mean you will more or less take over the loop via the list of pathes for validation into hibernates ClassValidator ?

Would be great - then we can throw away the customized SeamClassValidator ***cheers***