Re: [hibernate-dev] On possible extensions for the validator

Hi, I'm quite late in the game but I finally had a chance to look at your main paper http://www.ii.uib.no/publikasjoner/texrap/pdf/2009-389.pdf I quite like your approach for boolean composition. It is very elegant and can easily be added in a non breaking way to Hibernate Validator and Bean Validation. You guys are already prototyping it, so all good :) For cross-property validation, Hardy has reflected my position already. That being said, I wonder whether you can write your approach atop a generic class-level constraint @CrossValidation that would look for the properties annotations and behave as expected. That would be a nice way to offer both world to the users. You will need to "group" cross field constraints though: as I see it on the paper, you can only have one group of cross level constraint for a given constraint type per class. PS: I am not necessarily convinced by the all-but-one property is null use case though. I smells like a bad OO design in the first place that lead to such need. But I can be wrong :) Emmanuel On 22 sept. 2010, at 09:08, Federico Mancini wrote: