Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8171189 Deprecate ResourceBundleControlProvider for removal
  3. JDK-8171447

Release Note: Deprecate ResourceBundleControlProvider for removal

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Withdrawn
    • Icon: P4 P4
    • None
    • None
    • core-libs
    • None

      The Java Extension Mechanism has been removed and there is no longer a way to load the custom ResourceBundle.Control implementations through this SPI, as ResourceBundle.getBundle() is using ServiceLoader.loadInstalled() to locate them. A work around to achieve the old behavior is to explicitly pass a ResourceBundle.Control instance to ResourceBundle::getBundle

            naoto Naoto Sato
            naoto Naoto Sato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: