-
Bug
-
Resolution: Fixed
-
P2
-
7
-
b16
-
x86
-
windows_xp
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2150390 | 6u4 | Masayoshi Okutsu | P2 | Resolved | Fixed | b01 |
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.
There's no problem on UNIX/Linux.
- backported by
-
JDK-2150390 (rb) ResourceBundle.getBundle should ignore NoClassDefFoundError from ClassLoader on Windows
- Resolved
- relates to
-
JDK-6560126 (rb) OutOfMemoryError at ResourceBundle.java:1642 causes program to hang indefinitely
- Closed
-
JDK-6196068 Class.forName throws NoClassDefFoundError on miscapitalized classname
- Closed