beanvalidation/beanvalidation.org — comment on commit bc37cfec514b79f7695ccb35f9990115c5fdeab8
File: proposals/BVAL-241.md line 373
By gunnarmorling:

What I mean is that a constraint at a getter method can be interpreted as property-level bean constraint but also as method-level return value constraint. So it would be validated when calling `Validator#validate()` for the bean, but also when performing method-level validation when the getter is invoked by some code and the bean is enabled for method validation.

Now the question is whether this behavior is ok or not. In HV it's currently like that and so far I haven't seen any problems with that. But I think in OVal one can explicitly configure whether a constraint at a getter should be interpreted as invariant (property-level constraint), post-condition (return value constraint) or both. So maybe we should have something like this as well.