On 7 déc. 2011, at 22:32, Gunnar Morling wrote:
>> An additional idea would be some option to apply a
getter's>> constraints also as method parameter constraints on the
corresponding>> setter. So if method validation for that bean is enabled,
illegal>> values couldn't be set at all. Would that be useful?>> Global
setting or local setting?
Haven't thought that far :) Probably both would make sense. Globally
via the configuration API, locally via an annotation, for instance.
I'm personally not a big fan. I'm afraid of noisy constraints