-
Enhancement
-
Resolution: Incomplete
-
P3
-
None
-
9, 10
-
x86_64
-
linux
FULL PRODUCT VERSION :
Any java 9
java version "9.0.1"
Java(TM) SE Runtime Environment (build 9.0.1+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
for instance
A DESCRIPTION OF THE PROBLEM :
I'm creating this issue to follow on http://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8190696 which did NOT resolve the bug and abusively closed the ticket.
Factually Java 9 broke a feature for all applications preventing all ALL the code to be migrated on Java 9 and therefore adopt the platform.
There is no technical reason to do that (encapsulation is not technically valid since a custom classloader already breaks it fo rinstance).
This is a significant regression and breakage so please provide a way to fix it and at least a way to plug globally a ResourceBundleProvider (or control provider) to fix that blocking issue.
REGRESSION. Last worked in version 8u162
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Implement a custom ResourceBundleControlProvider and set it up on the JVM.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
All ResourceBundle usages - including named modules - should use the ResourceBundleControlProvider.
ACTUAL -
For named modules it is ignored.
REPRODUCIBILITY :
This bug can be reproduced always.
Any java 9
java version "9.0.1"
Java(TM) SE Runtime Environment (build 9.0.1+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
for instance
A DESCRIPTION OF THE PROBLEM :
I'm creating this issue to follow on http://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8190696 which did NOT resolve the bug and abusively closed the ticket.
Factually Java 9 broke a feature for all applications preventing all ALL the code to be migrated on Java 9 and therefore adopt the platform.
There is no technical reason to do that (encapsulation is not technically valid since a custom classloader already breaks it fo rinstance).
This is a significant regression and breakage so please provide a way to fix it and at least a way to plug globally a ResourceBundleProvider (or control provider) to fix that blocking issue.
REGRESSION. Last worked in version 8u162
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Implement a custom ResourceBundleControlProvider and set it up on the JVM.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
All ResourceBundle usages - including named modules - should use the ResourceBundleControlProvider.
ACTUAL -
For named modules it is ignored.
REPRODUCIBILITY :
This bug can be reproduced always.
- relates to
-
JDK-8190696 ResourceBundleControlProvider no more usable
-
- Closed
-