-
Enhancement
-
Resolution: Fixed
-
P4
-
5.0, 6
-
b38
-
generic, x86, sparc
-
generic, linux_redhat_7.2, solaris_8, windows_nt, windows_2000, windows_xp
Some developers would like the ability to define their own search strategies. For example, they would like to search for bundles in different packages, using the same bundle name. For example, getBundle("MyBundle", Locale.US) might look for this class in the following way:
1. search for packageA.res.en_US.MyBundle
2. then packageA.res.en.MyBundle
3. packageA.res.<default locale>.MyBundle
4. etc.
3. then packageA.res.MyBundle
Or perhaps they would like the bundles to exist in a database structure of some kind.
- duplicates
-
JDK-5086301 ResourceBundle.getBundle("...", locale) locale is ignored
- Closed
-
JDK-6463986 (rb) Unexpected behavior of ResourceBundle fallback mechanism
- Closed
-
JDK-4486664 RFE: ResourceBundle should fall back from zh_HK to zh_TW instead of to zh
- Closed
-
JDK-4812194 Suggest ResourceBundle.loadBundle check for .class before calling Class.forName
- Closed
-
JDK-4874079 Allow fast applet download when using PropertyResourceBundles and Jar indexing
- Closed
-
JDK-4075467 RFE: ResourceBundle should support resources other than .class or .properties formats
- Closed
-
JDK-4399413 ResourceBundle.getBundle should have better support for variants
- Closed
-
JDK-4782713 RFE: ResourceBundle should provide a less hard coded data path search strategy.
- Closed
- relates to
-
JDK-5049014 ResourceBundle.getBundle(): zh_TW locale should fallback to "en" locale
- Closed
-
JDK-5102289 (rb) ResourceBundle enhancements for Mustang
- Resolved
-
JDK-4668479 Option to turn off codebase lookup in AppletClassLoader during resource requests
- Resolved