Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
JSON default serializers for date/datetime differ javadsl to scaladsl
See original GitHub issueDefault JSON serializers for Lagom’s javadsl and scaladsl use different format when serializing java.time.Instant (this potentially impacts other date/datetime related classes).
online-auction-scala serializes bidTime in Bid instances using string/rfc3339 format.
online-auction-java serializes bidTime in Bid instances using a float representing seconds since epoch (with at least 2 decimals, maybe more?).
This issue is not to discuss what is the most appropriate format for each class in java.time but to settle and document the behavior of the default json serializers. Since each API uses a different underlying implementation (“jackson with JavaTimeModule” vs play-json) using differnt formats for same types could block interop between LagomJava and LagomScala.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think we should change the Jackson configuration to use RFC3339 - Swagger uses this, and I think it tends to be pretty standard across the web to use it. We should of course make it configurable, and not do it until a major release, documenting it in the migration guide.
This is fixed in #1955