Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support timezone configuration for Interval deserializer. #58

Closed
gordchen opened this issue Apr 3, 2015 · 2 comments
Closed

Support timezone configuration for Interval deserializer. #58

gordchen opened this issue Apr 3, 2015 · 2 comments
Milestone
2.6.0-rc4

Comments

@gordchen
Copy link

gordchen commented Apr 3, 2015

Can you support timezone configuration for the interval deserializer?
The default timezone may be not always the best choice when the interval is constructed from the milliseconds, the UTC is prefered in some cases.
@cowtowncoder
Copy link
Member

If that is useful and Joda handles it, may be possible. The main challenge is usually backwards compatibility, related to both handling of defaults (information missing), and in actual serialization format used. Contributions always welcome.

@islanderman islanderman mentioned this issue Jul 10, 2015
Closed
@cowtowncoder cowtowncoder added this to the 2.6.0-rc4 milestone Jul 13, 2015
@cowtowncoder
Copy link
Member

Implemented so that if timezone is specified via @JsonFormat, it will be set as the timezone of resulting Interval object; that is, as the timezone of start and end times.

cowtowncoder added a commit that referenced this issue Jul 13, 2015
@cowtowncoder
Implemented #58
726ed70
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.6.0-rc4
Development

No branches or pull requests
2 participants
@cowtowncoder @gordchen