-
Bug
-
Resolution: Duplicate
-
P3
-
None
-
1.1.6, 1.2.0
-
sparc
-
solaris_2.5.1
Name: rm29839 Date: 07/16/98
This bug was previously reported and closed as bug
4037093. It was closed as a duplicate of bugs
4069784 and 4059431 but should this is *wrong*.
See my comments at the end of 4037093, but briefly:
This bug does NOT relate to the well know default
time zone problem of Java. Instead, this bug is simply that
the TimeZone.java source interprets the zone id
"MET" to be "Iran Standard Time" or "Asia/Tehran"
whereas Solaris uses "MET" to mean
"Middle Europe Time". Please take a closer look
at this bug. Thanks!
(Review ID: 35210)
======================================================================
- duplicates
-
JDK-4210530 Date.toString() gives incorrect, GMT time
-
- Closed
-
-
JDK-4059431 Problem with the SystemTime on a Solaris Machine (Timezone = "WET")
-
- Closed
-
- relates to
-
JDK-4212004 TimeZone.getDefault() fails for EST time zone in Australia
-
- Resolved
-
-
JDK-4208984 Win32: Wrong default timezone in Melbourne Australia
-
- Closed
-