Deploying EAR with multiple EJB jars that fail to see registered session beans

[jmanko]

I have an EAR that I'm trying to deploy to Wildfly 8.1, and it's failing because one EJB module is failing to inject qualified session beans residing in another EJB module.  This is my first attempt at using Wildfly with an EAR project, so I'm just learning how WF handles module and dependency isolation.  Any help would be appreciated.

I basically have a WAR bean that injects a qualified EJB from my first EJB module:

WAR:

@Named

@SessionScoped

public class MyController {

  @Inject

  @MyCustom

  private MyEJBInterfaceLocal myInjectedBean; // <-- INJECTION WORKS, APPARENTLY

}

JAR LIBRARY:

@Local

public interface MyEJBInterfaceLocal { /* stuff */ }

EJB JAR #1:

@Stateless

@MyCustom // <-- CUSTOM QUALIFIER

public class MyCustomBean implements MyEJBInterfaceLocal {

  @Inject

  @MyDefault

  private MyEJBInterfaceLocal myInjectedBean; // <-- INJECTION FAILS

}

EJB JAR #2:

@Stateless

@MyDefault // <-- CUSTOM QUALIFIER

public class MyCustomBean implements MyEJBInterfaceLocal {

}

jboss-deployment-structure.xml:

<jboss-deployment-structure>

    <ear-subdeployments-isolated>false</ear-subdeployments-isolated>

</jboss-deployment-structure>

[jmanko]

Ok, I changed my initial injection point to inject the session bean qualified with @MyDefault, and that fails, too.  So, the problem is with the classes in my EJB #3 module, or my @MyDefault qualifier.  Though, the definitions for both qualifiers are the same with the exception of the name.  I double checked the final packaging, and everything seems ok.  Each project's pom machine except for their specific artifact name.  Their entries generated in application.xml match, and both are in the root of the final EAR package.  I see no discernible differences between EJB module #1 & #2 with the exception of their artifact names.

[tremes]

Hi John,

It seems to me that it should work, but MyController needs to implement java.io.Serializable. What is the error you are seeing during the deployment? What is the EJB #3 module you are referring above? Can you post your exact EAR structure (what all is in each module) ?  

[christian.beikov]

I had the same problem. Adding manifest entries in the web application module fixed it for me.

The ear-subdeployments-isolated flag does not seem to work in Wildfly 8.1.