Assumes all getX/setX methods are bean properties and errors with "wrong number of arguments"

Description

The code seems to assume that all methods which are named getX/setX are bean properties - even when they don't match the required constraints for a bean (i.e. no arg getter, single arg setter).

When using method validation, hibernate validator errors with a "wrong number of arguments" when it encounters annotated methods of this type which don't match the bean constraints.

The property detection should follow the JavaBeans specification.

Environment

None

Assignee

Hardy Ferentschik

Reporter

Dale Peakall

Labels

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Fix versions

Affects versions

Priority

Major
Configure