Scott Stark [http://community.jboss.org/people/scott.stark%40jboss.org] replied to the discussion "domain.xml work" To view the discussion, visit: http://community.jboss.org/message/535262#535262 -------------------------------------------------------------- Let's take a step back and review what we support today in 5.x. We have an api that exposes ManagedComponents for the deployment metadata that has been marked up as being part of the admin interface. This provides a facade on top of the implementation details of the deployers that transform the metadata into runtime components. There is an expectation that the ManagedComponent view is stable, but there is no enforcement of this. We have embedded JON using this API along with its own notion of components to expose the admin-console view of the ManagedComponents. this imposes something of an enforcement of the ManagedComponent since if the console breaks, jiras get raised and the incompatible change needs to be resolved. The domain.xml notion is essentially a unification of the embedded JON component descriptions into a single metadata view to allow for simple configuration of the server via scripting, etc. As such, a given domain.xml instance is just a series of ManagedComponent property updates. I view the domain.xml as just another "user" of the profile service ManagedComponent api. The following set of steps would each produce new sets of ManagedComponent property changes: 1. An initial domain.xml transforms the state of ManagedComponent properties from the new build state into some initial distribution state. There is a V1 repository of ManagedComponent property overrides. 2. embedded JON/JON updates provide a further set of changes. Where these properties intersect the metadata values of the domain.xml, it would have to be updated if we are going to allow direct editing of a server domain.xml. There is a V2 repository of ManagedComponent property overrides. 3. A rest client manipulates the current server domain metadata to push further updates. There is a V3 repository of ManagedComponent property overrides. There is only one authoritative store of ManagedComponent property edits that the profileservice implementation manages. Any physical domain.xml is a filtered view of this store. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/535262#535262] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]