Oh My ! I just noticed 7 monthes after that there was a reply to my concern (-_-) . Sorry every one for that.
Well I still want to discuss that point, because I find the subject interesting. Le mardi 5 juillet 2016 00:09:59 UTC+2, tsaloranta a écrit : > > > On Mon, Jul 4, 2016 at 9:26 AM, Oumar Aziz Ouattara <[email protected] > <javascript:>> wrote: > >> >> >>> >>>> Given >>>> my Local TZ being GMT+5 >>>> And >>>> default settings of jackson >>>> And >>>> the following *Local*DateTime 2000-01-01 06:00:00 >>>> When >>>> I serialize into a Json string >>>> Then >>>> Should I get ? >>>> >>>> 1. (1) {"jodaDateTime":"2000-01-01T06:00:00.000"} >>>> 2. (2) {"jodaDateTime":"2000-01-01T01:00:00.000Z"} >>>> 3. (3) {"jodaDateTime":"2000-01-01T06:00:00.000+05:00"} >>>> >>>> >>> > I think it should NOT be (3), as LocalDateTime should not, as per > definition, contain timezone or offset. > > I suspect that (1) would be ideal. However, it seems (based on issue > reports I have gotten) that for some reason date parsers appear to want to > get/generate a placeholder indicator of `Z` (or even +0000, which seems > incorrect). If so, there is the challenge of reading value back > appropriately. > > Still, it seems to me that (1) would be the optimal choice here. > > What do you think? > > -+ Tatu +- > > If we take the (1) choice, and send it to someone living at GMT+2, wouldn't we have lost the right information ? On the other hand, the choice made by the developer in choosing LocalDateTime is in itself on the assumption of keeping the TimeZone the same everywhere ... -- 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.
