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.

Sign up for GitHub

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

Jump to bottom

Problem with polymorphic types, losing properties from base type(s) #1125

Closed
cowtowncoder opened this issue Feb 10, 2016 · 2 comments
Closed

Problem with polymorphic types, losing properties from base type(s) #1125

cowtowncoder opened this issue Feb 10, 2016 · 2 comments
Milestone
2.7.3

Comments

@cowtowncoder
Copy link
Member

(background, see: dropwizard/dropwizard#1449)

Looks like sub-type resolution may be broken for one particular case: that of using defaultImpl. If so, appears like properties from super-types are not properly resolved; guessing this could be follow-up item for #1083 (even sooner than I thought...).
@cowtowncoder
Copy link
Member Author

While this could be related to #1128 that issue has now been resolved and there's no reproduction, so closing for now.

@cowtowncoder cowtowncoder changed the title Problem with polymorphic types, defaultImpl Problem with polymorphic types, losing properties from base type(s) Mar 1, 2016
@cowtowncoder
Copy link
Member Author

Second try: guessing this is related to handling of StdSubtypeResolver.

cowtowncoder added a commit that referenced this issue Mar 1, 2016
@cowtowncoder
further attempts to make test for #1125, still no luck.
0b449ff
@cowtowncoder cowtowncoder reopened this Mar 5, 2016
@cowtowncoder cowtowncoder mentioned this issue Mar 5, 2016
Closed
@cowtowncoder cowtowncoder added this to the 2.7.3 milestone Mar 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.7.3
Development

No branches or pull requests
1 participant
@cowtowncoder