JDK-8038436 : Re-examine the mechanism to determine available localedata and cldrdata
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2014-03-26
  • Updated: 2016-08-26
  • Resolved: 2014-09-02
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 9
9 b30Fixed
Related Reports
Relates :  
JDK-8151479 - Performance degradation in JDK 9 b30
Relates :  
JDK-8057646 - ClassCircularityError running SQE test
Relates :  
JDK-8058509 - CLDRLocaleDataMetaInfo should be in jdk.localedata
Relates :  
JDK-8057075 - Improve ability to diagnose JRE and CLDR locale provider adapter on resource bundle loading error
Relates :  
JDK-8048588 - Granularity of localedata and cldrdata
Description
The current mechanism to determine the available locale providers depends on the JDK layout, specifically it checks if localedata.jar and cldrdata.jar are present.

In JDK 9, localedata and cldrdata will be modules and there will be no localedata.jar and cldrdata.jar.

One option to consider is the use of ServiceLoader to load the CLDR and LocaleData providers.
Comments
Removed the file existence check for those jar files. Turned LocaleDataMetaInfo as an SPI, and dynamically search for the impl (i.e., localedata.jar and cldrdata.jar) at runtime through ServiceLoader.
22-08-2014