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/546605#546605 -------------------------------------------------------------- Here's a few more thoughts that fall out of this: 1. Management operations can be categorized by their type:1. Query operations which read a value 2. Update operations which change or add a value 2. Management operations can be organized into two scopes:1. Domain scope, which affect the domain object/XML model as a whole and (in the case of updates) are validated and then propagated to the relevant servers1. Only values which are configured at the domain level would be visible from the domain level; deployment specific values which were not present at the domain level would only be readable at the server scope 2. Although it is conceivable that we may decide that the DC must introspect all deployments and build a complete object model, this might or might not be practical implementation-wise1. But on the other hand, if we do this (effectively putting the functionality that is currently residing in the structure deployers into the DC), server startup would be lightning-fast because all the deployment information will be parsed out and validated already (and the servers wouldn't need to have those classes)... 2. Server scope, which *must not* affect the domain model in any way, and which take effect only on the server for which they are targeted, keeping in mind:1. Some operations might be applicable to a server group, for convenience (like retrying a deployment that failed across many servers in a group with the same failure cause, which an admin can perform when the underlying problem is fixed)1. Though this is realized as simply a broadcast of an operation across multiple servers, accumulating whatever responses come back 2. Extra-domain monitoring operations might fall into this category 3. All "actual" values that pertain to deployments would be readable at this level 4. All operations which pertain to transient run-time state (such as the failed deployment restart action I alluded to above, or other runtime administrative ops like killing connections or interrupting threads) would fall into this category Jason points out that having the DC parse out all deployments does have a lot of advantages, and I'm starting to agree with him. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/546605#546605] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]