1 Reply Latest reply on Aug 3, 2006 8:10 AM by jesla

    Deployment order and @Depends annotation

    jesla

      Hi,

      I have an ear package (named contact.ear) which classes I would like to use within another package (contactws.jar). Everything works fine if I first deploy the ear and then the another package. However, in normal situation (e.g. on server restart) the deployment order is different and contact.jar won?t deploy.

      My question is, could I influence the deployment order with @Depends annotation and if so, what parameters (i.e. ear=contact.ear, jar...) give?

      Regards, Matti

      2006-08-03 08:50:42,484 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/C:/jboss-4.0.4.GA/server/default/deploy/contactws.jar
      java.lang.NoClassDefFoundError: contactinfo/ejb/Info
       at java.lang.Class.getDeclaredMethods0(Native Method)
       at java.lang.Class.privateGetDeclaredMethods(Class.java:2365)
      


      Btw. contactinfo/ejb/Info is entity bean.

      --- Incompletely deployed packages ---
      org.jboss.deployment.DeploymentInfo@a1dbee32 { url=file:/C:/jboss-4.0.4.GA/server/default/deploy/contactws.jar }
       deployer: MBeanProxyExt[jboss.ejb3:service=EJB3Deployer]
       status: Deployment FAILED reason: contactinfo/ejb/Info
       state: FAILED
       watch: file:/C:/jboss-4.0.4.GA/server/default/deploy/contactws.jar
       altDD: null
       lastDeployed: 1154584242093
       lastModified: 1154584242062
       mbeans:
      



        • 1. Re: Deployment order and @Depends annotation
          jesla

          Hi,

          I managed to find a workaround for my problem: the trick was to package the contactws.jar into contactws.ear with appropriate application.xml.

          I can't say what exactly was wrong with the earlier attempt. Some sort of class loading/scoping issue I guess.

          Regards, Matti