Changing Default Time Zone in CalendarDeserializer?

[Brad Lohnes]

Hello,   I am new to the list and apologize if this question has already been answered – I spent a few hours searching for the issue but did not find it.   Here is the issue:   When converting XML dateTime types, axis converts to java.util.Calendar, which is fine. However, the implementation of CalendarSerializer hard-codes the time zone to “GMT” (and also hard-codes the format, as well).   We have implemented a web service using axis but have received a new requirement very late in the project (scheduled to finish testing this week). The requirement is that our web service assume not GMT at the interface endpoint, but rather another timezone (GMT+12:00). This means two things:   When we receive an XML dateTime element with no time zone information, we must assume our local time zone, not GMT. When serializing our own output, we are required to not include time zone information, and other services within the SOA are to assume local timezone information.   I am not interested in debating the merits of this design – our opinion has been made clear. Nevertheless, it is our requirement. J   How can we replace the existing axis functionality?   Is there a simple configuration option? (I have not found one) Is there a simple way to replace (through configuration) the CalendarDeserializer implementation with our own? Is there another option that has not been considered? Is the only option to replace the CalendarDeserializer class and compile axis ourselves? (We are currently working from the distribution library rather than compiliing from source ourselves).   Your urgent response in this matter would be greatly appreciated.   Regards,   Brad