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
olivergierke opened this Issue Feb 8, 2012 · 4 comments

Comments

Projects
None yet
2 participants
@olivergierke

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

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Feb 8, 2012

Member

Thanks for the bug report. Fixed in master.

Member

timowest commented Feb 8, 2012

Thanks for the bug report. Fixed in master.

@olivergierke

This comment has been minimized.

Show comment
Hide comment
@olivergierke

olivergierke Feb 8, 2012

It seems AnnotationMapper suffers from the same issue.

It seems AnnotationMapper suffers from the same issue.

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Feb 8, 2012

Member

AnnotationMapper fixed as well

Member

timowest commented Feb 8, 2012

AnnotationMapper fixed as well

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Feb 19, 2012

Member

released in 2.3.2

Member

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