[JDK-6380023] (tz) API: some TimeZone methods can't deal with GMT offset and DST rule changes - Java Bug System

Type: Bug
Resolution: Unresolved
Priority: P4
Fix Version/s: None
Affects Version/s: 1.4.0, 6
Component/s: core-libs
Labels:
None

Subcomponent:
java.util:i18n
Understanding:
Fix Understood
Introduced In Version:

1.1
CPU:

generic, x86
OS:

generic, windows_xp

TimeZone has methods that assume the GMT offset of a time zone would never change. However, it does change in the real world. That assumption causes problems especially with future changes. Those methods are:

getRawOffset()
getAvailableIds(int)

We need overloads that take a time stamp as:

getRawOffset(long)
getAvailableIds(int, long)

Note that Calendar.get(Calendar.ZONE_OFFSET) returns the correct GMT offset at the time represented by the Calendar instance.
getDSTSavings() has the same problem.
useDaylightTime() has the same problem.

duplicates

JDK-6645262 (tz) Australia/Perth TimeZone useDaylightTime() returns incorrect boolean (False)

Closed

JDK-8061439 Java should handle user defined TimeZone subclass instances supporting historic

Closed

relates to

JDK-5055567 (tz) TimeZone.getAvailableIDs(int) may produce inconsistent info with getRawOffset()

Resolved

JDK-6907174 Confusing ZoneInfo details displayed for Pacific/Fiji TZ

Closed

JDK-6936350 API clarification needed on useDaylightTime() for timezones that have defined usage dates

Closed

Assignee:: Naoto Sato

Reporter:: Masayoshi Okutsu

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 2006-02-01 18:30

Updated:: 2017-02-10 14:22

Imported:: 16/Sep/12 10:05 AM

Indexed:: 18/Jul/12 5:21 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates