"bstansberry(a)jboss.com" wrote : Re: resurrecting DeploymentPhase, that wouldn't help with my example case of a war in deploy-hasingleton/. The missing dependency in the example is deploy/jbossweb.sar (the web server) *not* deployers/jbossweb.deployer. (One of the things the war deployers do is establish a dependency on the web server.) So, the MC knows to wait to install the war beans until the webserver is available. But validating the "deploy-hasingleton" profile won't give the MC a chance to be patient. | | ... | | This validation thing is a pain in general; I vaguely recall some discussion with Scott about a similar issue a year or two back. Perhaps we should move away from automatically validating and instead make it part of the SPI? Let the caller decide when they want a validation check and what to validate? Yes we could let the caller decide if he wants to validate the profile or not, but i'm not really sure what exactly is failing for you. Maybe because of the mainDeployer.process() which is done after each profile ? As validating the profile does not validate the deployments. mainDeployer.checkComplete() is only done once after the profiles are activated. Maybe you want to commit your .profile files? so that i can take a look what exactly is failing ? But i've renamed the root.profile to embedded.profile ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205073#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...