David Lloyd [http://community.jboss.org/people/david.lloyd%40jboss.com] replied to the discussion "Profiles in domain.xml" To view the discussion, visit: http://community.jboss.org/message/546593#546593 -------------------------------------------------------------- Definitely. Yeah, that's exactly what I was getting at.  Though like I said, Scott indicated that we still need the ability to let administrators restrict the set of subsystems that are allowed to be active for a given server group.  But this is definitely not the same as specifying the subsystems that *will* be started up, so yes, I agree.  Though using "environment" might be too general a term? I'd rather localize the configuration overrides to an explicit deployment declaration.  This gets back to a previous post I made where I gave this example of a possible way to explicitly declare a deployment in XML:     <!-- An application deployment which is assigned to two server groups -->     <!-- Note the sha1 hash, so we know which version of my-app.ear to deploy -->     <deployment name="my-app.ear" sha1="12b4...2b42" server-groups="group1 group2">         <!--           ~ Now inside here, we can put all the overrides which apply to a specific deployment,           ~ using a format that is perhaps specific to each deployment type           -->     </deployment> Or perhaps "deployment-unit" is a better name. I see what you're getting at with "environments" - to add a level of indirection between deployment types and their capabilities - but I'm not sure that deployment type is the right association to make.  Wouldn't it make more sense to declare the capability restrictions on either a domain-wide or per-server-group basis?  It seems to me that forbidding the use of certain subsystems at a deployment level would be considerably more complex, and I'm not sure that there's a requirement driving that idea. For example something like this mockup:     <!-- Domain-wide whitelist -->     <subsystems>         <allow name="ejb"/>         <allow name="http"/>         <allow name="ws"/>         <!-- Everything else is denied -->     </subsystems>     <!-- The back-end servers do not have HTTP, so blacklist them -->     <subsystems server-groups="group1">         <deny name="http"/>     </subsystems> Then any deployment going to the server group which implies a requirement on a subsystem which is forbidden would receive a deployment error.  (Assuming I understand the use case correctly, that is.) One thing is certain though: we need to identify the subsystems in question so we know what set of capabilities we're talking about in the first place. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/546593#546593] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]