JDK-7171372 : (cal) locale's default Calendar should be created if unknown calendar is specified
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 8
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2012-05-24
  • Updated: 2012-10-29
  • Resolved: 2012-09-05
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.
8 b55Fixed
In JDK7, Unicode locale extensions were introduced and a calendar type can be specified for creating a Calendar, such as "th-TH-u-ca-buddhist". When an unknown (or unsupported) calendar is specified, the default calendar type of the locale should be used. For example, if "th-TH-u-ca-chinese" is given, the Thai Buddhist calendar should be created by Calendar.getInstance. Currently, a GregorianCalendar is created instead of the locale's default. There's the same problem with ja_JP_JP.

Run the new test developed for JEP 127 with latest JPRT build and JDK8 b62.

SUGGESTED FIX http://hg.openjdk.java.net/jdk8/tl/jdk/rev/131a683a2ce0

EVALUATION When any unknown calendar type is specified, Calendar.getInstance should perform the old and same Calendar creation in JDK6 and earlier.