Details
-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR18
-
None
Description
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
Attachments
Issue Links
- incorporates
-
WFNC-50 [GSS](7.1.0) use of WildFlyInitialContext with wildfly-config.xml throws javax.naming.NoInitialContextException
- Resolved
- is incorporated by
-
JBEAP-14496 (7.1.z) Upgrade WildFly Naming Client from 1.0.7.Final to 1.0.8.Final
- Closed