0 Replies Latest reply on Jun 17, 2005 11:54 AM by hisaibye

    Service Dependency configuration used with JBoss 3.2.3 is no

    hisaibye

      We have developed an Application with the structure described below

      test.ear
       test.jar
       test.war
       startup.sar
       META-INF
       jboss-service.xml
       META-INF
       jboss-app.xml
       application.xml




      In order to ensure that the MBean Services in the startup.sar gets started after the deployment of all the EJBs in test.jar, I had used the depends tag in the jboss-service.xml in the startup.sar as given below

      <?xml version="1.0" encoding="UTF-8"?>
      
      <server>
      
       <mbean code="test.Production" name="test.com:service=Production">
       <depends>jboss.j2ee:service=EjbModule,module=test.jar</depends>
       </mbean>
      
      </server>


      The configuration worked properly in jboss version 3.2.3. The Service MBeans were invoked after the deployment of the EJBs in test.jar.

      After migrating to JBoss 4.0.2, I could see that the dependency check is not enforced. (i.e) The Beans in the startup.sar get executed even before the EJBs are deployed.

      Any help would be appreciated.

      Thanks,
      Krish.