"bstansberry(a)jboss.com" wrote : "emuckenhuber" wrote : Hmm is the DeploymentManager enough for you then? | | Not sure about the overall scope of this question, so I'll reply separately. ;) | OK, now a bit more on the DeploymentManager in general and how it relates to the clustered deployment repository I'm working to get into 5.1. Basically my goal for 5.1 was to restore an equivalent to the old "Farm" feature where a local-filesystem based repository is aware of changes in content and replicates the changed content around the cluster. Primary target is people updating the repository content by copying a new version of a deployment into a directory. The DeploymentRepository.addDeploymentContent() method will also trigger replication around the cluster. So, if a DeploymentManager client loaded the "farm" subprofile and then called distribute(name, phase, url, true) the net result would be the content would be replicated to all nodes in the cluster. But, that wouldn't result in it getting deployed in all nodes, since that's a separate step. Getting it deployed in all nodes would require a clustered DeploymentManager impl, which isn't in the cards for 5.1. So, kind of half-way there. Bottom line, I think a tool written against the 5.1 code base would be better off independently working with each of the nodes in the cluster; i.e. let the tool coordinate getting the content distributed to and deployed on all nodes. Let the clustered deployment repository be the replacement that people have requested for the non-tooling based Farm service. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210480#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...