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.

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

DateTimeSerializer should take the configured time zone into account #21

Closed
pavax opened this issue Sep 2, 2013 · 3 comments
Closed
Milestone

Comments

@pavax
Copy link

pavax commented Sep 2, 2013

At the moment the com.fasterxml.jackson.datatype.joda.ser.DateTimeSerializer writes the following code if the WRITE_DATES_AS_TIMESTAMPS feature is disabled:
...
jgen.writeString(value.toString());
...
whereas value is the DateTime object. However this doesn't take the configured timezone into account which might be set in ObjectMapper.setTimeZone(TimeZone timeZone).

A similar Issue was fixed for the DateTimeDeserializer see: #14

pavax pushed a commit to pavax/jackson-datatype-joda that referenced this issue Sep 2, 2013
cowtowncoder added a commit that referenced this issue Dec 21, 2013
Issue #21: DateTimeSerializer use the configured time zone
@cowtowncoder
Copy link
Member

Fixed for 2.3.1.

@Macarse
Copy link

Macarse commented Mar 6, 2018

@cowtowncoder
Copy link
Member

@Macarse thanks, added it there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants