ld be nice to get some feedback.
Thanks,
Federico Mancini
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Hi again,
I was just wondering whether I should interpret the lack of answers as
"no, this is not interesting at all", or as "we have a lot of other
things to do and do not have time for this right now"?
Federico
Den 22.09.2010 09:08, skrev Federico Mancini:
>Hi
> }
>
> 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
&g
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
> wrote:
>
>> Hi again,
>> I was just wondering whethe
oup esplicitely
when the annotation is used in the code (but still, it would be easier
to make suh a group the default group for the annotation at declaration
time, which would re-create the problem).
Den 11.10.2010 12:01, skrev Hardy Ferentschik:
> On Wed, 06 Oct 2010 17:53:38 +0200
Hi,
we managed to implement a first version of boolean composition for the
validator, and it seems to require very few changes to the code.
We also opened an issue on Jira about that.
From the tests we ran, the constraints seem to be evaluated correctly,
but we have some strange behaviour re
Ok now I see it.
Using groups for cross-validation is a very nice solution to be able to
reuse them on multiple sets of properties.
Then in Emmanuel's example I guess it should be
@AtLeastOneNotNullAmongst(groups={Group1.class,Group2.class})
B getB() { ... };
The @CrossValidation annotation at
Den 19.10.2010 10:06, skrev Emmanuel Bernard:
> Cross validation marker annotations like @ExactlyOneNull are not really
> actual constraints (ie annotated with @Constraint) because somehow they must
> carry two logic:
> - the property checking logic
> - the "aggregation" logic
> Besides the
