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

serializeWithType on BeanSerializer does not setCurrentValue #878

Closed
chikim79 opened this issue Jul 28, 2015 · 1 comment
Closed

serializeWithType on BeanSerializer does not setCurrentValue #878

chikim79 opened this issue Jul 28, 2015 · 1 comment
Milestone

Comments

@chikim79
Copy link

Related to issue #631
BeanSerializer is using BeanSerializerBase's serializeWithType and it is not setting the currentValue.

currentObject is always null when serializing an object that is declared as a subtype.

chikim79 pushed a commit to nfl/jackson-databind that referenced this issue Jul 28, 2015
@cowtowncoder
Copy link
Member

Thank you for reporting this. It is likely that there are other places where this might happen, so please let us know if others are found.

@cowtowncoder cowtowncoder added this to the 2.5.5 milestone Jul 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants