"emuckenhuber" wrote : Well i think so about xml defined profiles. I mean most of our deployments should come from a "commons/*" location, which leaves the user there with a mostly empty deployers, deploy, farm folder. | Therefore those profiles would be immutable (no addContent, hd scanning). | I guess there will be still the usual folders, where you can add custom deployers, deployments yourself. | And of course i did not say that those cannot be clustered. Just immutable, for our bundled stuff :) Yeah, if content is stored in "common/**" it's a bit off if one of the profiles started using that shared content then updates the content to match another node in the cluster. At least we shouldn't ship a configuration that works that way. But I'm pretty sure some people will reconfigure stuff so that happens. :) After all use of common/** is just a mechanism to reduce our download size. I doubt many people are actually booting multiple production instances off the same unzipped JBoss distribution. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214300#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...