-
Notifications
You must be signed in to change notification settings - Fork 54
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
@JsonDeserialize.contentConverter
does not work for non-builtin collections
#92
Comments
Belongs under Guava datatype library since this requires support by deserializers provided there; will transfer. |
Would be great to have a test case, if anyone wants something easy to do. Implementation should not be difficult either, need to have a look at default |
But isn't this a bug in common code? |
Should I submit my testcase in a form of PR adding unit test? |
@mwisnicki Unlikely based on your mentioning that it works for built-in collections? Guava datatype provides its own Immutable-type deserializers which need to handle a few aspects wrt customizations and configuration. If it turns out the problem happens to be in |
Yes, PR for the unit test would be a great start! It does not have to be separate if you (or anyone else) can figure out the fix too but it can be. |
@JsonDeserialize.contentConverter
does not work for non-builtin collections
Fixed by @JooHyukKim -- will be in 2.15.0. (and if anyone wants to backport fix in 2.14 that'd be fine too, looks safe enough) |
I'm trying to use content converter with Guava collections like so:
However this does not seem to do anything despite Jackson having deserializers for Guava.
Changing collection to one of built-in types makes the program work.
I would expect that if Jackson can deserialize given collection type, it will also be able to apply converters to it.
Posting here rather than to datatypes project since this is not related to specific collection implementation but rather a generic problem.
TestImmutableListContentConverter .java
pom.xml
The text was updated successfully, but these errors were encountered: