[jboss-dev-forums] [Design of POJO Server] - Re: Clustered DeploymentRepository for 5.1

"emuckenhuber" wrote : But i don't think a deploymentRepository is required for all profiles (e.g. the bootstrap profile, or in future most of the xml defined profiles). Not so sure about the "in future most of the xml defined profiles" part. Most of the stuff currently in deploy/ could logically go in farm/ and thus get the behavior of a newly starting node automatically syncing the subprofile content with the cluster.[1] That implies that in the xml defined profiles, most of the subprofiles could logically use clustering behavior, even those that specify deployers. At least conceptually that's true; whether we'd ever configure things that way in a stock config is a different issue. But I bet users will try it even if we don't. [1] One of the things I'm going to do locally as a test this week is move most of the stuff out of deploy/ into farm/; just leave the deploy/cluster stuff needed to let the clustered deployment repository work. Start the server and see what happens. :-) anonymous wrote : I mean in the end it's then depending on your implementation what it should support and if it uses a deploymentRepository. Very true. And AFAICT it shouldn't be a big deal to have a DeploymentRepository backed profile that also isn't "mutable" after startup. So I don't think having a Profile impl that isn't backed by a repository breaks anything for me; it's just another impl. I'm mostly just trying to point out some of the subtleties of my use case here so you know about them. :-) anonymous wrote : Just that the isMutable() is used by the DeploymentManager to determine which profiles are a possible target to deploy content to. | But i don't think i have time to do that for 'Beta1', but most probably for CR1. | Yeah, keep it simple. :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214255#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...