Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
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?
The text was updated successfully, but these errors were encountered:
yes it looks like a bug. We should definitely filter static methods in the BeanWrapper#buildFieldGraph() method.
Sorry, something went wrong.
#89 Exclude static and abstract methods from getter / setter resolution
I've commited a fix for this, it should be available in nightly build shortly.
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?
#89 - exclude static and abstract method from elligible setters and g…
Good point for you @facboy thanks.
This should be good now.
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)
No branches or pull requests