3 Replies Latest reply on Dec 10, 2012 3:15 PM by sacarro

    Classloading Issues


      I am deploying an inbound/outbound enabled resource adapter (test.rar) and an Singleton Session EJB in a standalone jar (ejb-test.jar).


      Within the resource adapter, I have included an ironjacamar.xml that defines the connection definition. When I deploy the rar, I see the connection factory get bound to the correct JNDI name.


      Within the EJB, I include in MANIFEST.MF the line "Dependencies: deployment.test.rar", and additionally annotate the Singleton Session Bean with "@ResourceAdapter("test.rar")". Within tje Singleton Session Bean class, I have an @Resource annotation with the mappedName property set to the bound name from the resource adapter deployment.


      When I deploy the EJB however, I still get a class not found exception from the @Resource injected class. Am I missing a step? I am running with the latest 7.1.1 JBoss AS baseline. I have also tried using the jboss-ejb3.xml with no luck.

        • 1. Re: Classloading Issues

          Use nightly snapshot before reporting problems

          • 2. Re: Classloading Issues



            Thanks for the quick reply. I did that with the downloaded artifact here: https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/ which is 7.2.0.Alpha1-SNAPSHOT. I am not sure that is 100% correct because I don't see it in the main panel: https://ci.jboss.org/hudson/view/JBoss%20AS/


            I get the same error however which makes me feel that I am missing a piece to the puzzle. Nothing seems to error out or report problems in the log (logging is set to debug). Is there a log statement that would tell me whether it is trying to load from the resource adapter or if it cannot find the resource adapter I am requesting?


            I followed you help here:




            So if that has changed then I am off the path.



            • 3. Re: Classloading Issues



              I ended up adding a META-INF/jboss-deployment-structure.xml that included


              <?xml version="1.0" encoding="UTF-8"?>

              <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">



                                            <module name="deployment.test.rar" slot="main" />





              That seems to resolve the class loading issue.