Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8247321

NamingManager.getInitialContext requires clarity for SPI mechanism

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Not an Issue
    • Affects Version/s: 9
    • Fix Version/s: None
    • Component/s: core-libs

      Description

      Customer complains the ServiceLoader mechanism introduced still looks for the Context.INITIAL_CONTEXT_FACTORY environment property when META-INF/services/javax.naming.spi.InitialContextFactory has a valid
      implementation.

      And if Context.INITIAL_CONTEXT_FACTORY environment is undeclared, it throws an NoInitialContextException

        Attachments

          Activity

            People

            Assignee:
            kravikumar Kiran Sidhartha Ravikumar (Inactive)
            Reporter:
            shadowbug Shadow Bug
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: