java.util.Date serialized as epoch millis after Spring Boot 3.5.x / CAP 4.4.x upgrade #56
Unanswered
LakshmiTN129
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
After upgrading to Spring Boot 3.5.x and CAP Java / CDS 4.4.x, all java.util.Date fields in our DTOs that used to serialize as ISO strings (e.g., "2024-06-01T00:00:00.000+00:00") are now serialized as epoch milliseconds ("1714521600000").
Tried approaches that didn’t work:
spring.jackson.serialization.write-dates-as-timestamps=false
spring.jackson.use-jackson2-defaults=false
@jsonformat or @JsonSerialize on DTO fields
Are there alternative approaches recommended in CAP 4.4.x for enforcing ISO 8601 globally?
Beta Was this translation helpful? Give feedback.
All reactions