JDK-6572242 : (rb) ResourceBundle.getBundle should ignore NoClassDefFoundError from ClassLoader on Windows
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2007-06-21
  • Updated: 2011-03-08
  • 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.
6u4Fixed 7 b16Fixed
Related Reports
Relates :  
Relates :  
The 6560126 fix includes a change to throw all Errors from ClassLoader, which caused a behavior change. When there are a class and a properties file which have the same bundle name in different case, such as "Config.class" and "config.properties", a class loader throws "java.lang.NoClassDefFoundError: config (wrong name: Config)" on Windows. Previously this Error was ignored in ResourceBundle.getBundle and "config.properties" was loaded successfully. However, ResourceBundle.getBundle fails to load the properties file after the 6560126 change.

There's no problem on UNIX/Linux.

EVALUATION NoClassDefFoundError should be ignored to be compatible.