Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSelma raises mapping field error for static methods #89
Comments
|
yes it looks like a bug. We should definitely filter static methods in the BeanWrapper#buildFieldGraph() method. |
slemesle
added a commit
that referenced
this issue
Apr 18, 2016
|
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? |
slemesle
added a commit
that referenced
this issue
Jul 15, 2016
|
Good point for you @facboy thanks. |
|
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) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?