Yes, I think we'll have to add a describe/prepare method as the caller needs to be able to receive meaningful information about what is wrong if a deployment cannot be described. In terms of being aware of cluster membership changes, that still needs to be added and how that is handled defined. There could be more interaction between the server and client side DeploymentProgress, but its possible that the DeploymentManager is not talking to live servers. I would view the cluster as locked at the start of the deployment op, and new additions need to synchronize their repository view once the op is complete. "bstansberry(a)jboss.com" wrote : | BTW, will the basic profile service impl still exist in 5.0.0.GA? | Yes, I expect so. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153803#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...