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

Hi Frederico, sorry for the late reply. I finally had some time to read through your paper. I think there are strong similarities between you work and Hibernate Validator or more specific the Bean Validation specification (JSR 303). Property validation in the SHIP Validator is basically the same as in Bean Validation. And what you call cross-annotations would be a class level validator in Bean Validation terms. Bean Validation also offers constraint composition similar to what is described in your paper. What Bean Validation does not offer is a boolean composition of the constraints. Here conjunction of constraints is always assumed. We are not able to do something like this: @BoolTest(BoolType.OR) @Null @Max(10) @Target({ METHOD, FIELD }) @Retention(RUNTIME) @Constraint(validatedBy = { }) public @interface NullOrMax { public abstract String message() default "foo"; public abstract Class<?>[] groups() default { }; public abstract Class<? extends Payload>[] payload() default { }; @OverridesAttribute(constraint = Max.class, name = "value") public abstract long max() } Also the ability to validate a subset of all properties from within a class level validator sounds interesting. We could implement these features as Hibernate Validator specific extensions. Are you interested in getting involved? --Hardy On Tue, 05 Oct 2010 09:48:15 +0200, Federico Mancini <mancini_federico(a)yahoo.it&gt; wrote: