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

DeserializationProblemHandler.handleUnknownTypeId() returning Void.class, enableDefaultTyping causing NPE #2221

Closed
MeyerNils opened this issue Jan 11, 2019 · 1 comment
Closed

DeserializationProblemHandler.handleUnknownTypeId() returning Void.class, enableDefaultTyping causing NPE #2221

MeyerNils opened this issue Jan 11, 2019 · 1 comment

Comments

@MeyerNils
Copy link
Contributor

Returning Void.class from com.fasterxml.jackson.databind.deser.HandleUnknowTypeIdTest.testDeserializationWithDeserializationProblemHandler().new DeserializationProblemHandler() {...}.handleUnknownTypeId(DeserializationContext, JavaType, String, TypeIdResolver, String) is causing a NPE in jackson 2.9. I'll provide a pull request illustrating the issue in a test.
@MeyerNils MeyerNils mentioned this issue Jan 11, 2019
Merged
@cowtowncoder
Copy link
Member

Thank you for reporting this! I'll have a look.

@cowtowncoder cowtowncoder changed the title handleUnknownTypeId with Void.class, enableDefaultTyping and generic Collections not working as expected DeserializationProblemHandler.handleUnknownTypeId() returning Void.class, enableDefaultTyping causing NPE Jan 18, 2019
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
No milestone
Development

No branches or pull requests
2 participants
@cowtowncoder @MeyerNils