NamingManager.getInitialContext requires clarity for SPI mechanism

XMLWordPrintable

      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

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

              Created:
              Updated:
              Resolved: