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

wildfly-naming-client can't be used against older servers (which don't contain it)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 7.1.0.DR12
    • 7.1.0.DR8
    • EJB, Naming
    • None

      When doing a remote lookup on an older server version which doesn't contain wildfly-naming-client itself, it fails with

      javax.naming.NamingException: Failed to lookup [Root exception is java.io.IOException: java.lang.ClassNotFoundException: org.wildfly.naming.client.SimpleName from [Module "org.jboss.remote-naming:main" from local module loader @42f30e0a (finder: local module finder @24273305 (roots: /home/hudson/hudson_workspace/workspace/eap-7x-ejb-client-qa-tests-elytron/2648bbaa/jboss-eap-7.0/modules,/home/hudson/hudson_workspace/workspace/eap-7x-ejb-client-qa-tests-elytron/2648bbaa/jboss-eap-7.0/modules/system/layers/base))]]
      

      If wildfly-naming-client is about to completely replace jboss-remote-naming, it needs to be fully backward compatible and work against older server versions.

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

              Created:
              Updated:
              Resolved: