Spring JSON converter converting date format "yyyy-MM-dd'T'HH:mm:ss.SSSXXX" to OffsetDateTime without offset

Question

I been receiving date in the "yyyy-MM-dd'T'HH:mm:ss.SSSXXX" format from JSON input, which gets converted to a DTO by Spring it self. But when converted to OffsetDateTime instance, this loses the information about Offset in the created OffsetDateTime instance. For example we are passing following in the Postman invoking an API, this results in the parsing and object getting created but the object doesn't have offset set in it. Below is the example of the "2019-03-21T06:43:56.235+11:00" date when parsed it results in the date with OffsetDateTime instance but it doesn't have the +11:00 as the offset. When I directly parse this string using DateTimeFormatter I am able to get the offset populated. below is the code that uses DateTimeFormatter. OffsetDateTime.parse(offSetDateTimeString, DateTimeFormatter.ofPattern(DATE_PATTERN)) The DATE_PATTER = "yyyy-MM-dd'T'HH:mm:ss.SSSXXX". Please guide. Thank you. UPDATE My DO has following objects: @Id @GeneratedValue(strategy = GenerationType.AUTO) private int id; private String name; // THis won't work as it doesn't support timestamp. // @Column(columnDefinition = "TIMESTAMP WITH TIME ZONE") // private LocalDateTime localDateTime; @Column(columnDefinition = "TIMESTAMP WITH TIME ZONE") private ZonedDateTime zonedDateTime; @Column(columnDefinition = "TIMESTAMP WITH TIME ZONE") private OffsetDateTime offSetDateTime; While DTO also has same fields with SAME data types. JavaScript questions and answers, JavaScript questions pdf, JavaScript question bank, JavaScript questions and answers pdf, mcq on JavaScript pdf, JavaScript questions and solutions, JavaScript mcq Test , Interview JavaScript questions, JavaScript Questions for Interview, JavaScript MCQ (Multiple Choice Questions)

Answer 1

Okay, here is what I did to solve this issue. Instead of accepting OffsetDateTime in DTO, I accepted String. For this I required changes to be done in the Mapper (MapStruct). I defined custom String to OffsetDateTime mapper classes and specified them in the uses in @Mapper. This solved my parsing related issue, then moving on to the DB, I noticed a couple of things. TIMESTAMP WITH TIME ZONE doesn't store the date in the exact given format. You need to use the ZoneId to convert the time to appropriate timezone. And you have to write custom Utility for this kind of conversion. We need to obtain now the relevant timezone's zoneId object, which we have currently obtained from the incoming request. This is the update as of now. Posting this for other's reference. Thank you all for guiding.