<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[I&#x27;m seeing weirdness around timestamps and I use jackson]]></title><description><![CDATA[<p dir="auto">We use jackson to serialize and deserialize timestamps we receive from FusionAuth webhooks and we're seeing issues with the year being far in the future. The year is in the 56000 range.</p>
<p dir="auto">What's going on?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/187/i-m-seeing-weirdness-around-timestamps-and-i-use-jackson</link><generator>RSS for Node</generator><lastBuildDate>Tue, 15 Sep 2026 18:45:37 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/187.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 24 Jun 2020 14:50:23 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to I&#x27;m seeing weirdness around timestamps and I use jackson on Wed, 24 Jun 2020 14:56:30 GMT]]></title><description><![CDATA[<p dir="auto">Apparently jackson + friends make assumptions when it comes to parsing raw -&gt; ZonedDateTime. It appears that the ZonedDateTime for createInstant when deserializing timestamps are not being handled properly somehow, so you need custom code. We have our own Jackson serializer and deserializer for ZonedDateTime to ensure we always get milli in and milli out.</p>
<p dir="auto">Here's the <a href="https://github.com/inversoft/jackson5" rel="nofollow ugc">code</a> (Apache2 license) and the <a href="https://mvnrepository.com/artifact/com.inversoft/jackson5" rel="nofollow ugc">maven repository links</a> if it's helpful.</p>
]]></description><link>https://fusionauth.io/community/forum/post/470</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/470</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Wed, 24 Jun 2020 14:56:30 GMT</pubDate></item></channel></rss>