-
1. Re: Start background process on the startup of the Application
ctomc Oct 1, 2015 5:49 AM (in response to fmontada)Your configuration just configures classloading dependances not the order of deployment
for that you need to add jboss-all.xml
see http://stackoverflow.com/questions/25605968/how-to-set-deployment-order-of-two-ears-in-wildfly
-
2. Re: Start background process on the startup of the Application
fmontada Oct 1, 2015 1:11 PM (in response to ctomc)Hi Tomaz
thanks for reply
We do not have two .ear /
application.ear
-META-INF
-jboss-app.xml
-jboss-deployment-structure.xml
-application.xml
-lib
-startup.sar
-app1.war
-app2.war
The problem is that we need to initialize some background process ( config, audit .....) before the app1.war and app2.war are deploy,
e,g
execute our background process ( config, audit .....) deploying startup.sar, then after it is done then start deploying app1.war then app2.war
Could you help us ?
Best
Francisco
-
3. Re: Start background process on the startup of the Application
ctomc Oct 1, 2015 1:33 PM (in response to fmontada)it doesn't matter if you have ear, sar, war, jar, rar, ... deployment the principal is the same.
-
4. Re: Start background process on the startup of the Application
fmontada Oct 1, 2015 3:08 PM (in response to ctomc)Hi Tomaz thanks for replay
We did the config below and did not works,
application.ear
-META-INF
-jboss-all.xml
-jboss-app.xml
-jboss-deployment-structure.xml
-application.xml
-lib
-startup.sar
-app1.war
-app2.war
<jboss xmlns="urn:jboss:1.0">
<jboss-deployment-dependencies xmlns="urn:jboss:deployment-dependencies:1.0">
<dependency name="startup.sar" />
</jboss-deployment-dependencies>
</jboss>We can not find jboss-all.xml on this list
Deployment Descriptors used In WildFly - WildFly 8 - Project Documentation Editor
we are missing something ?
Thanks for the help
Francisco
-
5. Re: Start background process on the startup of the Application
jameslivingston Oct 4, 2015 8:02 PM (in response to fmontada)You should be able to use <initialize-in-order>true</initialize-in-order> in your application.xml to force it to initialise the sub-deployments in the order listed in that file. That way an @Startup @Singleton EJB or similar kind of thing would be initialised before any later modules are.