JDK-4825902 : The jvm looks for _en.properties under C locale
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_8
  • CPU: generic
  • Submitted: 2003-02-28
  • Updated: 2003-03-01
  • Resolved: 2003-03-01
Related Reports
Duplicate :  
JDK-4426761 - Multiple, unnecessary, GET requests to the web server for a Property file
Description
When application run under C locale, the jvm will try to find xx_en.properties 
first, if can't find then use xx.properties. 
Since our application provides xx.properties, the jvm should directly go and
pick them up in C locale instead of looking for xx_en.properties. It
creates unwanted error message. (see also BugID 4426761)
Comments
EVALUATION Java doesn't have a C locale. According to the java.util.Locale specification, locales are identified by a language code, a country code, and a variant (the empty string is allowed for either one). The Java runtime therefore maps the Solaris C locale to its nearest Java equivalent, the "en_US" locale, as the default locale. This is intentional and not a bug. If an application doesn't like this default, it can change it using Locale.setDefault or pass an explicit locale argument to ResourceBundle.getBundle. Since this bug report also takes issue with error messages as described in bug 4426761, I'm closing this bug as a duplicate. ###@###.### 2003-02-28
28-02-2003