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

EJB client doesn't work with connections configured in wildfly-config.xml

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 7.1.0.DR16
    • 7.1.0.DR15
    • EJB

      META-INF/wildfly-config.xml snippet:

      <configuration>
          <authentication-client xmlns="urn:elytron:1.0">
              <authentication-rules>
                  <rule use-configuration="default"/>
              </authentication-rules>
              <authentication-configurations>
                  <configuration name="default">
                      <allow-all-sasl-mechanisms/>
                      <set-mechanism-properties>
                          <property key="wildfly.sasl.local-user.quiet-auth" value="true"/>
                      </set-mechanism-properties>
                  </configuration>
              </authentication-configurations>
          </authentication-client>
          <jboss-ejb-client xmlns="urn:jboss:wildly-client-ejb:3.0">
              <connections>
                  <connection uri="remote+http://127.0.0.1:8080" />
              </connections>
          </jboss-ejb-client>
      </configuration>
      

      EJB client code snippet:

      Properties props = new Properties();
              props.put(Context.INITIAL_CONTEXT_FACTORY, WildFlyInitialContextFactory.class.getName());
      InitialContext ctx = new InitialContext(props);
      String lookupName = "ejb:/server/HelloBean!ejb.HelloBeanRemote";
      HelloBeanRemote bean = (HelloBeanRemote)ctx.lookup(lookupName);
      

      This doesn't work. EJB client library doesn't seem to take the connection configuration into account at all and doesn't try to connect anywhere, just fails with the universal EJBCLIENT000024 error.

            dlloyd@redhat.com David Lloyd
            jmartisk@redhat.com Jan Martiska
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: