Timestamp format - bug in DelayInformationProvider

When using the API to connect to an Oracle Real Time Collaboration server the ‘‘stamp’’ attribute returned by the server is not correctly handled by the API. The format used is yyyy-MM-dd’‘T’‘HH:mm:ss (e.g. 2006-10-27T16:30). Code in the API (like the DelayInformationProvider) tries UTC_FORMAT, NEW_UTC_FORMAT and then yyyy-MM-dd’‘T’‘HH:mm:ss’‘Z’’.

The ‘‘Z’’ is causing a problem. One alternative would be to delegate this ‘‘figure out what time format to use’’ logic to a utility class. This class could attempt all four formats until one worked. Ideally it should remember what format worked the last time and attempt to use that format, so that the performance overhead of exception handling is reduced.