I observed that when jax-b is used with JAX-WS, the Calendar Datatype is converted to XMLGregorianCalendar which is expected in jax-ws. But a difference in time-zone is observed with this migration where the time-zone was not normalized to UTC.
Also following are the references that says XSD 1.1 dataTime datatypes retain the Server time-zone information unlike converting to UTC in XSD 1.0.
I'm trying to generate a wsdl using Websphere specific wsgen tool which has the xsd version as 1.0 . I'm curious to know why the XSD 1.0 dateTime datatype retaining the server time-zone.
I'm wondering if this really matters. These two times are the same, they are just represented differently. 2019-01-21T09:15:14.633Z is the same as 2019-01-21T09:15:14.633+00:00 which is the same as 2019-01-21T16:15:14.633+07:00. Any well functioning client will treat the two as the same value.