"bstansberry(a)jboss.com" wrote : | One concern with the validate is you can get unsatisfied dependencies. Say you have a war in deploy-hasingleton. And say during the 'all' profile deploy the cluster/deploy-hasingleton-jboss-beans.xml file is deployed before jboss-web.sar. That will trigger activation of the deploy-hasingleton profile, and the war will not complete deployment pending dependency on jboss-web.sar. Not a problem, since at the end of the whole thing the dependency will be satisfied and the war will deploy. Except, the validate call during the deploy-hasingleton activation will throw an exception. Hmm yes i understand your concern - in general PS is about managing profiles it does and should not really care about the actual type of deployments in a profile. Which basically means that you also need corretly defined profiles :) This leads a bit into the implicit/explicit dependcies and deployment ordering. Basically all profiles need to declare their dependencies - this might get a bit redundant. Therefore implicit dependencies based on ordering. So all profiles defining deployers (maybe also mixed with some runtime beans related to it) need to be activated/deployed first. Your clustering profile would need to get deployed after this like same for a hot-deployment profile. At the moment the legacy behavior of PS is still there - so deploy is activated after deployers, and therefore your HASingleton basically activates the profile correctly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204970#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...