-
Enhancement
-
Resolution: Fixed
-
P4
-
1.2.2, 1.2.2_007, 1.3.0, 1.3.1, 1.3.1_19
-
None
-
beta
-
generic, x86, sparc
-
generic, solaris_2.6, solaris_7, solaris_9, solaris_10
We have to always update timezone data every year, if the one we have now is correct. This is not good implementation. Also, all the timezone data is hardcoded in TimeZone data. This is lack of maintainancability. TimeZone data will change a lot year by year. Since it's just each country local data.
koushi.takahashi@japan 1999-07-27
- duplicates
-
JDK-4388302 Test of the correct handling of the Solaris host time zone
- Closed
-
JDK-4358472 TimeZone:inDaylightTime doen't pass.
- Closed
-
JDK-4505478 Incorrect Daylight Savings for JDK 1.2 and JDK 1.3
- Closed
-
JDK-6515180 Some 2006 dates showing wrong results regarding DST with 1.3.1_19 JDK
- Closed
-
JDK-4496763 Sydney daylight saving must begin in September, not August
- Closed
-
JDK-6471271 (tz) New DST rules for North America not yet added to 1.3.1
- Closed
- relates to
-
JDK-4328065 InDayLightTime returns false for Australia/Sydney in September
- Closed
-
JDK-6391777 JDK 1.3 TZ fix required - Related to SUN BASE RFE 6332148
- Resolved