You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With addition of (meant to be) helpful failure for Joda and Java 8 date/time types (latter via #2683) things work kind of ok for common case -- if no (de)serializer found for one of these types, exception given tries to suggest a solution.
Alas it appears that there is alternative means -- #2795 -- to provide for (de)serialization support with just using mix-ins, but which is not consider, so this new feature essentially breaks something that works in 2.10 and 2.11 (latter at least in 2.11.3).
It'd be good to figure out additional check to avoid this: either based on finding mix-in(s) for target type or, for deserializers, existence of non-default Creator?
The text was updated successfully, but these errors were encountered:
Went with "if there is a mix-in targeting specific type, do not construct failing (de)serializer": works for specific case; will deal with other problems if and when they are encountered.
(for background see #2683 and #2795 )
With addition of (meant to be) helpful failure for Joda and Java 8 date/time types (latter via #2683) things work kind of ok for common case -- if no (de)serializer found for one of these types, exception given tries to suggest a solution.
Alas it appears that there is alternative means -- #2795 -- to provide for (de)serialization support with just using mix-ins, but which is not consider, so this new feature essentially breaks something that works in 2.10 and 2.11 (latter at least in 2.11.3).
It'd be good to figure out additional check to avoid this: either based on finding mix-in(s) for target type or, for deserializers, existence of non-default Creator?
The text was updated successfully, but these errors were encountered: