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.
- relates to
-
JBEAP-7105 jboss-remote-naming doesn't work at all in 7.1.0.DR8
- Closed
-
JBEAP-8914 (7.1.0.DR12) jboss-client.jar cannot be used for remote JNDI lookup - "javax.naming.OperationNotSupportedException: WFNAM00026: No provider for found for URI: null"
- Closed