"adrian(a)jboss.org" wrote : The best way to write these tests would be use a test-config | that starts with the all configuation but without anything in deploy. | | You then deploy an ear that includes everything, | * a war | * an ejb2 | * an ejb3 | * an mdb | * a rar | * a datasource | * an mbean | * a pojo | | Then you deploy all the files from all/deploy and test the application works. | | But then you repeat the test, by undeploying all/deploy and then redeploying | them in a different permutation. | | Not only does this test that dependencies are working across all | our deployments, it also checks they can be stopped and restarted. | e.g. There is a known issue with EJB2 where this fails | https://jira.jboss.org/jira/browse/JBAS-5332 Ok, but if there will be none in the deploy dir, the ear will not be able to deploy successfully, because there will be no services such as jbossweb, transaction manager etc. as I mentioned earlier. Or will the AS wait for other deployments to finish the deployment of the ear? Even if that deployments will not be in the deploy dir in that time? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178232#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...