"E" in MET means "Eastern" in Java, "Europe" in Solaris

Name: mc57594 Date: 03/06/97


Lines 257 and 258 in TimeZone.java:

        // MET is the ID for Middle East Time timezone.
        new SimpleTimeZone((int)(3.5*millisPerHour), "MET"),

In the zoneinfo file from solaris: (/usr/share/lib/zoneinfo/europe)
# 1:00 MET+DST Middle Europe

If the TZ environment variable is set to MET, Solaris will show
the middle european time, Java programs will use the middle
eastern time when using the default time zone.

I'm not sure if the behaviour is correct in Java or in Solaris,
but they definitely should not differ.

company - Union Bank of Switzerland , email - ###@###.###
======================================================================

[Sheri Good 03/10/97] Here is some more confusion on MET.

Category: java
Subcategory: classes_util
Bug/rfe/eou: bug
Synopsis: MET is *not* "Middle East Time"
Severity Impact: (internal)
Severity Functionality: (internal)
Priority: (internal)
Description:
  Hi,

In java.util.TimeZone your TimeZoneData uses the ID "MET" for
"Middle East Time" - it's actually "Middle Europe Time". The
JVM correctly sets the user.timezone property to MET for me,
but then using the Calendar gives completely bogus times...

  Cheers,

  Ronald

company - , email - ###@###.###
Work around:

Comments:
customer_rec: new
Company: other
Employee:Ronald Tschalaer
Release: jdk11
Hardware Version: sun4u
O/S version: sol2.5.1
User Role: D
User Type: E
Sun Contact: (internal)
end_customer_rec:
BUG_END