Influencing Deployment Order

[benabernathy]

I have a short term task of porting a legacy EAR containing a WAR and a set of EJBs (version 3) from JBoss 4.2.3.GA to 7.1.1.Final. The war contains web services developed using Axis 2. The problem I'm having is the web service code accesses the EJBs (all stateless session beans and entity beans) by doing a JNDI lookup. I was able to modify the lookup to handle the changes between how 4 and 7 register the JNDI names for the beans. The problem I'm now seeing appears to be that the web services are starting up before all of the EJBs are registered. Is it possible to influence the deployment order so that I can be guaranteed the EJBs are all registered before the web services are deployed?

Any direction/advice would be greatly appreciated.

[tepih78]

It seems that if JEE level 6 with initialize-in-order parameter is used then the modules will be initialized in order they are defined in application.xml.

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

<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" version="6">

  <display-name>myapp_Ear<display-name>

  <initialize-in-order>true</initialize-in-order>

  ...

</application>

Hope that helps!

[benabernathy]

That appeared to change the deployment order. Thank you for the reply.