I am using the EAR suffix setting order in conf/bootstrap/deployers.xml . The value ranges from 50 (started first) and 950 (last started), see the LegacyDeploymentContextComparator class . In your case, you will receive:
<bean name="topContextComparator"> <constructor factoryClass="org.jboss.system.deployers.LegacyDeploymentContextComparator" factoryMethod="getInstance"/> <property name="suffixOrder" class="java.util.Map"> <map keyClass="java.lang.String" valueClass="java.lang.Integer"> <entry> <key>web-services.ear</key> <value>500</value> </entry> <entry> <key>enterprise-app.ear</key> <value>600</value> </entry> </map> </property> </bean>
I also use a common suffix configuration such as _<N>.ear , where <N> is the initial order. This avoids changing the deployers.xml file each time a new EAR is deployed. This is useful when deploying versions of MyEar_v20130611_3.ear such as MyEar_v20130611_3.ear (in this case N = 3):
<entry> <key>_1.ear</key> <value>500</value> </entry> <entry> <key>_2.ear</key> <value>600</value> </entry> <entry> <key>_3.ear</key> <value>700</value> </entry>
source share