Skip to content
New issue

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? Sign in to your account

JDBC - DefaultMapper should consider fields from complete class hierarchy #95

Closed
odrotbohm opened this issue Feb 8, 2012 · 4 comments
Closed

Comments

@odrotbohm
Copy link

@odrotbohm odrotbohm commented Feb 8, 2012

DefaultMapper currently uses Class.getDeclaredFields() to inspect the given object for fields. Unfortunately this doesn't include fields from superclasses so that not the entire data of the object will pe persisted. This should be replaced by Class.getFields() or at least be configurable.

timowest added a commit that referenced this issue Feb 8, 2012
@timowest
Copy link
Member

@timowest timowest commented Feb 8, 2012

Thanks for the bug report. Fixed in master.

@odrotbohm
Copy link
Author

@odrotbohm odrotbohm commented Feb 8, 2012

It seems AnnotationMapper suffers from the same issue.

@timowest
Copy link
Member

@timowest timowest commented Feb 8, 2012

AnnotationMapper fixed as well

@timowest
Copy link
Member

@timowest timowest commented Feb 19, 2012

released in 2.3.2

@timowest timowest closed this Feb 19, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants