On Tue, Mar 20, 2018 at 4:49 AM, Ruwen Schwedewsky < [email protected]> wrote:
> Hi! > > I wasn't sure whether to send an email here and to submit a bug, so I hope > this is the right spot. > > I am currently using Jackson 2.4 and a mixture of JodaTime and Java 8 > time. Since Joda is deprecated, I want to move away from it. I am also in > the process to upgrade Jackson to 2.9.4. > > One "issue" I can across is that with jodatime, I always get three > subsecond digits, no matter what. Example: > > 2016-12-06T23:29:41.760Z > > With the latest Jackson version and Java 8, I get the same time as: > > 2016-12-06T23:29:41.76Z > > While this is according to ISO 100% correct, I have a public API and I > can't be 100% sure that all the API users have a ISO-compliant parser. I > know how to change the formatting but I guess I might not be the only one > with that situation out there. Would you accept a PR for that? > > I would add a new SerializationFeature and add it to the > ZonedDateTimeSerializer and the OffsetDateTimerSerializer. > I think I would prefer configuration of module in this case, and not a `SerializationFeature`, as this seems quite specific to date/time types, and actually just one module. But aside from that, sure, assuming `DateFormat` definition is not enough to force specific behavior. I think Java 8 seems to have some oddities like this. -+ Tatu +- > > Cheers > Ruwen > > > -- > You received this message because you are subscribed to the Google Groups > "jackson-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
