1 Reply Latest reply on Mar 1, 2010 12:23 PM by Vicky Kak

    (JBoss 5.0.0 EAP) - RAR contained in EAR no longer deployed before EJB Jars

    Shane McEneaney Newbie
      I have an EAR containing EJB JARs and three RARs. In JBoss 4.2.3 the deployment order was RARs followed by EJB JARs. This is a requirement as some of the MDBs and EJBs depend on the ResourceAdapters contained in the RARs.

       

       

      In JBoss 5 the deployment order has changed. The EJB JARs are deployed first and then subsequently the RARs. I have attempted using strict module deployment ordering but this no longer works. In addition, I have added @Depends annotations to my MDBs but this does not work either.

       

       

      If I disable my MDBs and allow JBoss to start without them I can see all of the the EJBs and MDBs in my application being deployed followed by my ResourceAdapters.

       

       

      Is there any way to force JBoss to deploy an EJB Jar after all RARs as in JBoss 4.2.3?
        • 1. Re: (JBoss 5.0.0 EAP) - RAR contained in EAR no longer deployed before EJB Jars
          Vicky Kak Master

          smceneaney wrote:

           

          In JBoss 5 the deployment order has changed. The EJB JARs are deployed first and then subsequently the RARs. I have attempted using strict module deployment ordering but this no longer works.

          It is known issue with JBoss5 and if you are using EAP then talk to support team they would be able to give you one off patch.

          https://jira.jboss.org/jira/browse/JBAS-7106

           

          If you are not using EAP then you will have to create one off patch for it, you can find the details from the above pointed JIRA.

           

          smceneaney wrote:

          In addition, I have added @Depends annotations to my MDBs but this does not work either.

           

           

          If I disable my MDBs and allow JBoss to start without them I can see all of the the EJBs and MDBs in my application being deployed followed by my ResourceAdapters.

           

          You should be able to set it via Depends annotaton, don't know what wrong is going on. Do you have a test case to explain it?

           

          You can also try using prefix deployment sorted in JB5, check this JIRA

          https://jira.jboss.org/jira/browse/JBAS-7614

           

          I know it is much of backporting of features, can't help on that.