-
1. Re: overriding deployment startup order on boot
jmsjr Jan 23, 2014 2:24 AM (in response to robdeheer)Something like this:
The above will allow you control over the startup of EARs.
However, rereading your original question, it seems that you actually want to control startup of modules __within__ an EAR. That's already possible with the @DependsOn annotation.
-
2. Re: overriding deployment startup order on boot
wdfink Jan 23, 2014 2:22 AM (in response to robdeheer)Did you mean modules or deployed applications?
For modules you need to set the correct dependencies in the module.xml
-
3. Re: overriding deployment startup order on boot
robdeheer Jan 23, 2014 2:33 AM (in response to wdfink)I meant deployed applications.
-
4. Re: overriding deployment startup order on boot
erasmomarciano Jan 23, 2014 5:38 AM (in response to robdeheer)I don't understand your task
Probably you mean this:
http://www.mastertheboss.com/jboss-deploy/configuring-jboss-as-7-deployment-order
-
5. Re: overriding deployment startup order on boot
wdfink Jan 23, 2014 12:17 PM (in response to robdeheer)You might add a jboss-all.xml to your EAR file, you'll find examples if you search for.
-
6. Re: overriding deployment startup order on boot
robdeheer Jan 27, 2014 7:45 PM (in response to wdfink)I was not able to get the jboss dependency config to work correctly. I hit some lib dependency issues where myear.ear has classpath dependencies on libs.war as well as an application deployment dependency on primarydependency.ear. All of the deployments depend on libs.war.
I'm going to try some variations with eap-6.2. My initial iterations were on 6.1.
Thanks for your help,
Rob