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

Release Note: Deprecate ResourceBundleControlProvider for removal

    XMLWordPrintable

Details

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

    Description

      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

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: