-
Bug
-
Resolution: Fixed
-
P3
-
6
-
b07
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2106957 | 5.0u4 | Yuka Kamiya | P3 | Closed | Fixed | b03 |
| JDK-2187330 | 1.4-pool | Sean Coffey | P4 | Closed | Won't Fix |
The getAvailableIDs(int) method should be consistent with getRawOffset() which returns the GMT offset of the time zone at the current time. Currently, getAvailableIDs(int) assumes the last known GMT offset.
###@###.### 2004-06-01
JCK test case TimeZone2014 checks consistencies between the time zone offset given to TimeZone.getAvailableIDs(int) and the retrun value of TimeZone.getRawOffset() of each time zone returned by the getAvailableIDs(int) call. TimeZone0003 could be affected if time zone's future GMT offset change is related to min or max values.
###@###.### 2004-06-01
JCK test case TimeZone2014 checks consistencies between the time zone offset given to TimeZone.getAvailableIDs(int) and the retrun value of TimeZone.getRawOffset() of each time zone returned by the getAvailableIDs(int) call. TimeZone0003 could be affected if time zone's future GMT offset change is related to min or max values.
- backported by
-
JDK-2106957 (tz) TimeZone.getAvailableIDs(int) may produce inconsistent info with getRawOffset()
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Open
-
-
-
- Closed
-
-
JDK-5054346 Support tzdata2004a
-
- Closed
-