-
Notifications
You must be signed in to change notification settings - Fork 82
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
Can't deserialize a serialized DateTimeZone with default typing #82
Milestone
Comments
Thank you for reporting this. Is this reproducible on 2.7.2? |
Yep - sorry, should have mentioned which versions I tested against, here's the POM:
|
No prob, thanks! |
Just needed to basically force type information to use abstract type |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying to serialize a DateTimeZone instance, then deserialize it back afterwards; it always fails. Looks like it's due to the fact that there is no type mapping for CachedDateTimeZone (indeed for any of the subclasses of DateTimeZone) and no String constructor, combined with our project's use of default typing on serialized objects.
Result:
Obviously, a simple workaround is to create a mix-in just for DateTimeZone that disables typing only for it. The following test passes:
The text was updated successfully, but these errors were encountered: