Normalizing time zones in XML with WebSphere Process Server
RayTseng 100000KB37 Visits (7790)
Over the past few weeks, I've seen multiple questions related to the DateTime field and time zones with WebSphere Process Server. The question is why does the timezone get normalized in WebSphere Process Server?
The DateTime field in the original message is usually a local timezone set as: <Due
The key point to remember is that the serialization that WebSphere Process Server uses is one of many possible XML messages. However, the value it has chosen is valid and conforms to XML specifications. So, if your destination service conforms to the full XML apecifications, it should be able to understand and treat the DateTime field exactly the same no matter if it is provided in UTC or a local time zone format.
From a logical point of view, any of the time zones still represent the same point in time. It is the same situation as why the numbers "1.0", "1.00" , and "01.0" are all equal in XML.
There are an infinite number of different possible options that you might want related to the format of the XML message, which is beyond the scope of what can be reasonably provided by the product. As other example, we have run across requests for WebSphere Process Server to customize
Each of these requests for customizations actually reveal a deficiency in the consuming service not being able to fully understand the XML specification and logically equivalent XML messages. Because there are an infinite amount of options, an architectural decision was made to not provide these customization options, but only ensure that we will provide a message that is valid and logically equivalent.