-
Enhancement
-
Resolution: Fixed
-
P3
-
6
-
None
-
b43
-
generic
-
generic
Due to the current ResourceBundle seach mechanism, after the base bundle found, a list of locale specific resource bundle has to be located, e.g. resourceX_en.class (if not found, resource_X.property will be searched).
Most of time, these locale specific resource bundle do not exists and the side effect of doing the search of non-existent resources will result into the opening of every jar file on bootclasspath and extention classpath.
We could speed up the above process by using the ResourceBundle.Control API available in 1.6 to provide a list of locales we known for sure exists and we ONLY search these locale specific resource bundle. Some experiments show doing this will give us a great improvement on cold startup, at least on Windows platform.
###@###.### 2005-06-03 23:40:43 GMT
Most of time, these locale specific resource bundle do not exists and the side effect of doing the search of non-existent resources will result into the opening of every jar file on bootclasspath and extention classpath.
We could speed up the above process by using the ResourceBundle.Control API available in 1.6 to provide a list of locales we known for sure exists and we ONLY search these locale specific resource bundle. Some experiments show doing this will give us a great improvement on cold startup, at least on Windows platform.
###@###.### 2005-06-03 23:40:43 GMT
- relates to
-
JDK-6291925 Update class lists for class data sharing
- Resolved
-
JDK-6299235 User-localized resource files not found after perf optimization for awt/swing resources
- Resolved
-
JDK-4911220 Reduce loading time for awt resources
- Closed
-
JDK-6530694 Menu-internationalization differs from Java 5.0
- Closed
-
JDK-6278974 Add meta-index to jre/lib
- Resolved