-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
11
-
generic
-
generic
ADDITIONAL SYSTEM INFORMATION :
Windows 11
A DESCRIPTION OF THE PROBLEM :
Reconsider re-openingJDK-8190696
"ResourceBundleControlProvider no more usable"
The fact that it can't be used in module environment makes it hard or very hard to block the default fallback mechanism. Such a functionality was offered by: ResourceBundle.Control getNoFallbackControl(...) which allowed one to easily inspect if translation is missing for a specific language and override the default fallback mechanism to tell that fallback should be different DURING THE CALL TO THE STANDARD getBundle().
I will not insist on returning to the same API, but some API which could control it would be great.
ACTUAL -
Be able to block fallback mechanism in an easy way.
CUSTOMER SUBMITTED WORKAROUND :
instead of:
ResourceBundle.getBundle("x")
use
ResourceBundle.getBundle("x_pl") for "pl" locale.
FREQUENCY : always
Windows 11
A DESCRIPTION OF THE PROBLEM :
Reconsider re-opening
"ResourceBundleControlProvider no more usable"
The fact that it can't be used in module environment makes it hard or very hard to block the default fallback mechanism. Such a functionality was offered by: ResourceBundle.Control getNoFallbackControl(...) which allowed one to easily inspect if translation is missing for a specific language and override the default fallback mechanism to tell that fallback should be different DURING THE CALL TO THE STANDARD getBundle().
I will not insist on returning to the same API, but some API which could control it would be great.
ACTUAL -
Be able to block fallback mechanism in an easy way.
CUSTOMER SUBMITTED WORKAROUND :
instead of:
ResourceBundle.getBundle("x")
use
ResourceBundle.getBundle("x_pl") for "pl" locale.
FREQUENCY : always
- relates to
-
JDK-8190696 ResourceBundleControlProvider no more usable
-
- Closed
-