Juan José Olmedilla Arregui created JBJCA-923: ------------------------------------------------- Summary: RAR (inbound adapter) inside EAR does not see JAR files in EAR/lib Key: JBJCA-923 URL: https://issues.jboss.org/browse/JBJCA-923 Project: IronJacamar Issue Type: Bug Components: AS Environment: JBoss As 7.1.2 (EAP) Windows 7 and Windows Vista Reporter: Juan José Olmedilla Arregui Assignee: Jesper Pedersen -I have a RAR file and EJB JAR inside my EAR. The RAR includes several JAR libraries only used by it which are packed within it. - The EJB JAR includes an MDB that receives the inbound messages from the Resource Adapter and therefore needs to have access to the same MessageListener interface which is in the common JAR file library included in EAR/lib. - The RAR has a dependency on the common MessageListener interface included in the JAR file sitting in EAR/lib - The project is a maven multi-module project using maven jar (for the commong library where the interface is), ejb, ear and rar plugins - Things I have tried: 1. Including "compile" dependency to the common jar in both, the EJB JAR and RAR. It does not work because it includes two copies of the jar, one in the EAR/lib and one inside the RAR, it deploys but later it fails when a message is received because there are two different bytecodes for the same class. 2. Including a Dependency in the MANIFEST of the RAR pointing to deployment.EARNAME.ear.MYLIBNAME.jar. It does not find that dependency 3. Including a Dependency in the MANIFEST of the RAR pointing to deployment.EARNAME.ear.lib.MYLIBNAME.jar. It does not find that deployment 4. Including the dependency as "provided" in the EJB project as in the RAR, including in both MANIFEST's a dependency on "deployment.MYLIBNAME.jar" and deploying separately the MYLIBNAME.jar and EARNAME.ear. This works but I want a solution that allows me to pack everything in one single EAR file -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira