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

Content of jboss-client.jar does not provide required features

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • 7.1.0.DR8, 7.1.0.DR12
    • EJB, JMS, Naming, Remoting
    • None
    • Regression, Blocks Testing

      jboss-client.jar in EAP 7.1.0.DR8 contains jboss-remote-naming.jar which is not possible to use for JNDI lookup from EAP 7.1.0.DR8 server (issue JBEAP-7105) because it must use newer wildfly-naming-client.jar.
      wildfly-naming-client.jar is not compatible with older EAP 6.x/7.0.z releases (JBEAP-7266) and breaks backward compatibility which was requested and provided in scope of RFE EAP7-78 for EAP 7.0.0.GA.

      Additionally jboss-client.jar in EAP 7.1.0 should be backward compatible with different security and remoting implementations in EAP 6/7.z. The above holds for corresponding wildfly-ejb-client/wildfly-jms-client boms.

      This is regression against EAP 7.0 and (testing) blocker for EAP 7.1.0. Purpose of this jira is to recover to required state.

              dlloyd@redhat.com David Lloyd
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: