Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-12283

[GSS](7.2.0) use of WildFlyInitialContext with wildfly-config.xml throws javax.naming.NoInitialContextException

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 7.1.0.DR18
    • EJB, Naming
    • None

      If a client use WildFlyInitialContext without properties the following Exception is thrown:
      Exception in thread "main" javax.naming.NoInitialContextException
      at org.wildfly.naming.client.WildFlyInitialContext.getDefaultInitCtx(WildFlyInitialContext.java:65)
      at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:350)
      at javax.naming.InitialContext.lookup(InitialContext.java:417)
      at org.jboss.wfink.eap71.playground.wildfly.client.WildFlyICConfigClient.main(WildFlyICConfigClient.java:33)

      It is expected that this works according to https://github.com/wildfly/wildfly-naming-client#usage.
      The reproducer can be found here
      https://github.com/wfink/jboss-eap7.1-playground/blob/master/clients/WildFlyConfig/src/main/java/org/jboss/wfink/eap71/playground/wildfly/client/WildFlyICConfigClient.java

            jondruse@redhat.com Jiri Ondrusek
            rhn-support-wfink Wolf Fink
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: