JDK-6638110 : (tz) TimeZone.getDisplayName(...) spec is inconsistent with implementation for unavailable locales
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 6,6u7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_xp
  • CPU: generic
  • Submitted: 2007-12-05
  • Updated: 2017-05-16
  • Resolved: 2011-03-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7 b116Fixed
Related Reports
Duplicate :  
JDK-6695566 - (tz) JCK test api/java_util/TimeZone/index.html#getDisplayName: Fails on machines with GMT timezone
Relates :  
JDK-6955047 - (tz) javadoc for TimeZone.getDisplayName(boolean daylight, int style, Locale locale) is not clear
Description
The spec for TimeZone.getDisplayName(...) says: "If the display name is not available for the locale, then this method returns a string in the normalized custom ID format."
In fact the methods return TimeZone.getDisplayName(Locale.ENGLISH) for unavailable locales.
Comments
EVALUATION The spec needs to clarify the behavior: the default Locale search path is used. In addition, exceptions should be described correctly.
11-12-2007