anonymous wrote : DeploymentStages.REAL would be too far as real runtime components would start to be created. Maybe we would just need to run it through the DESCRIBE phase, maybe PRE_REAL. The main problem is a disconnect between a system that looks valid in terms of everything being there, vs actually having all of the runtime components in place. Yes, REAL is too far, at least right now. :) I said real based on this comment in DeploymentStages | /** The installed stage - could be used to provide valve in future? */ | DeploymentStage INSTALLED = new DeploymentStage("Installed", REAL); where I interpreted the "valve" as being the notion Adrian described in an old thread of bringing a deployment all the way to being ready to handle requests, and then at the last stage switching JNDI refs, connectors, etc to use the new version. But we're clearly not ready for that yet. :) anonymous wrote : There really is no one controlling entity other than the admin layer. The admin layer calling the profile service api to do the deployment is what triggers everything, dealing with failures and rolling back to the previous version, but all participants need to be properly written with dependencies in place to allow a failure to be unwound. anonymous wrote : So by running the deployments across the cluster to the DeploymentStages.DESCRIBE phase, we know whether or not all dependencies can be satisfied. The only possible coordinator is the admin layer driving the profile service api usage. Maybe your driving at, do we want this to be an old farming deployment type of service? No, I was being muddleheaded. In Vegas we agreed that it's going to be the admin layer that drives this. In the 2 years since I've just been looking at MainDeployer and the deployers and got my thinking in a muddle. I need to look more at the DeploymentManager API; sounds like that's where ability to do things like "running the deployments across the cluster to the DeploymentStages.DESCRIBE phase" will be exposed. anonymous wrote : So I think we need to look at a FarmServiceUnitTestCase that uses the profile service DeploymentManager to validate the various types of things that can happen with a two node deployment say, and figure out what will/won't work for the initial release. Sounds good; that will be my focus. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153036#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...