-
Notifications
You must be signed in to change notification settings - Fork 117
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
Custom LocalDate
deserializer not being used with 2.11, jsr-310 datatype module
#177
Comments
Running the above code leads to the following exception:
|
Since support for Java 8 date/time types is provided by separate module, will transfer to its issue tracker. |
LocalDate
deserializer not being used with 2.11, jsr-310 datatype module
First things first: unless you ask But you are actually extending deserializer from that package so I don't think this is what happens. You are instead calling |
Realize this doesn't solve your present issue, but as a side note (and note to self), there is some related work started to allow |
Pardon, I've found the probleem and it's indeed not a bug. Between 2.10.4 en 2.11.0 the deserializer now uses the following method:
Which creates a new deserializer, replacing my custom deserializer.
|
Ok, glad you figure out the issue. Sub-classing is quite fragile, unfortunately, and composition is encouraged, for this reason. |
Dear Jackson team,
It seems that as of Jackson 2.11 my custom (date) deserializer is no longer being used by the object mapper. I've tried various ways of registering the deserializer but none seem to work. In the previous version (2.10.4) this was not a problem.
Strangely the JSR310 LocalDateDeserializer is being detected and registered automatically from the classpath, skipping the deserializer in my custom module.
Example:
The text was updated successfully, but these errors were encountered: