Selma raises mapping field error for static methods

[facboy]

The mapping code seems to be picking up static methods on the bean class (eg getX, isY) and complaining that they are not mapped. This seems like it should be a bug?

[slemesle]

yes it looks like a bug. We should definitely filter static methods in the BeanWrapper#buildFieldGraph() method.

[slemesle]

I've commited a fix for this, it should be available in nightly build shortly.

[facboy]

I'm not sure the fix is entirely right, maybe I'm thinking unclearly but won't it only exclude methods that are both static and abstract, not either/or?

[slemesle]

Good point for you @facboy thanks.
This should be good now.

[facboy]

actually I missed a problem, why are we excluding abstract methods? this breaks my code now as some of my source beans have abstract methods that are implemented in a sub-class (eg google autovalue)