[kepler-dev] [Bug 5602] Timezone confusion using the scheduler

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5602

--- Comment #1 from Jing Tao <tao at nceas.ucsb.edu> 2012-05-30 10:01:46 PDT ---
We added two drop-down boxes for both the start and end time. Users can use the
boxes to choose time zone names.

In order to avoid the locale issues, the time zone ids will be communicated
between the clients and servers. I verified the time zones ids used English
even though the machine had the Chinese Locale.

However, the time zone ids have a slight difference among different java
versions. So it is possible that a server can't understand a time zone id from
a client if their java versions are different. I had to add a new API in the
Scheduler Server so client can use it to get time zone ids from the server.
Those ids will be used in the communication. So this will make sure that server
can understand the time zone ids. Also the client will cache those time zone
ids in order to improve performance.

If there is no time zone id parameter in the client's request (e.g.,
kepler-2.3), the scheduler server will use the default value -- its local time
zone.

I tested the new feature and it worked to me. I will leave it open until Derik
tests it.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.