[jboss-jira] [JBoss JIRA] (WFLY-8801) Legacy EJB client dependency in wildfly-feature-pack breaks AS TS

[Josef Cacek (JIRA)]

Josef Cacek created WFLY-8801:
---------------------------------

             Summary: Legacy EJB client dependency in wildfly-feature-pack breaks AS TS
                 Key: WFLY-8801
                 URL: https://issues.jboss.org/browse/WFLY-8801
             Project: WildFly
          Issue Type: Bug
          Components: EJB, Test Suite
            Reporter: Josef Cacek
            Priority: Critical


The new jboss-ejb-client-legacy dependency in wildfly-feature-pack POM breaks AS TS client tests. Users can hit this issue if they define dependencies using the feature-pack pom.

{code:xml}
        <dependency>
            <groupId>org.wildfly</groupId>
            <artifactId>wildfly-feature-pack</artifactId>
            <type>pom</type>
        </dependency>
{code}
The testsuite/shared has a dependency on wildfly-feature-pack POM which newly introduces the legacy EJB client dependency. (https://github.com/wildfly/wildfly/pull/10061/files) It results in classpath issues.

When I hit the issue in my test, the test prints just this exception and the testsuite run hangs forever:

{code}
Exception in thread "XNIO-1 task-14" java.lang.NoSuchMethodError: org.jboss.ejb.client.Affinity.forUri(Ljava/net/URI;)Lorg/jboss/ejb/client/Affinity;
	at org.jboss.ejb.protocol.remote.ProtocolV3ObjectResolver.<init>(ProtocolV3ObjectResolver.java:43)
	at org.jboss.ejb.protocol.remote.EJBMarshallingCompatibilityHelper.getObjectResolver(EJBMarshallingCompatibilityHelper.java:42)
	at org.wildfly.naming.client.remote.RemoteClientTransport$1.handleMessage(RemoteClientTransport.java:155)
	at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:434)
	at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:897)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)
{code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)