-
-
Notifications
You must be signed in to change notification settings - Fork 142
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
investigate test code that passes in jackson-module-scala v2 but not in v3 #536
Comments
@cowtowncoder there is a test that is failing in jackson v3 but not in v2.
When I try to deserialize
jackson-module-scala v2 and v3 has very similar code in its AnnotationIntrospector. The jackson-databind v3 code for collecting properties (POJOPropertyBuilder) has changed quite a lot in v3. I could try hacking at the fields, getters and setters that the Scala module code exposes to jackson-databind but I fear this will cause more issues than it solves. A similar test in java works ok so the issue only happens with jackson-module-scala. One of the oddities of Scala is the |
@cowtowncoder I hacked a fix in jackson-module-scala v3 - it now needs to check the JsonProperty annotation itself instead of relying on jackson-databind to do that |
Hmmh. That is unfortunate, assuming it by-passes |
@cowtowncoder the change I made was in the Scala AnnotationIntrospector. It should be ok to just leave the v3/master code as is since the test case passes now. |
Ah ok. That makes sense then -- I just want to try to avoid code from outside an |
//TODO fix
in test codeThe text was updated successfully, but these errors were encountered: