The main problem is to differentiate a method from a getter in such universe where you throw the convention out the window.

On 14 Jun 2017, at 06:12, Andrei Sereda <> wrote:


Apologies  if I hijack this mailing list. Please redirect me to right DL / forum, if it is the case.

I would like to inquire if custom method resolution is within the scope of the spec (or exists already) for beans which don't exactly follow JavaBean convention. By custom, I mean name() vs getName(). 

I've noticed, lately, the trend to use code generators (Immutables, FreeBuilder, AutoValue etc.) for domain entities. By default they all use name() for getters (instead of getName()) :

@FreeBuilder public interface Person {
@NotBlank String name();
@Min(16) int age(); .... }

It would be nice if BeanValidation could support such use-case via pluggable (getter / setter) method resolver (for example).

Associated JIRA  ticket HV-1363

Thanks in advance,
beanvalidation-dev mailing list