David Lloyd [http://community.jboss.org/people/david.lloyd%40jboss.com] replied to the discussion "domain.xml work" To view the discussion, visit: http://community.jboss.org/message/545361#545361 -------------------------------------------------------------- This opens the door to new ideas.  If the domain.xml (including deployment listing) represents the current state of the domain, and server managers (SM) sync this down, why not make it a versioned database?  Then, if a SM comes up after some changes were made on the domain controller (DC), the SM can pull down only the differences, just like database replication.  This is good in the case of a very complex configuration with many deployments (the SM only has to pull down deployments that it needs [as defined by the domain.xml] *and* that it doesn't already have).  It may also allow something like atomic deployment, where multiple deployment units *and/or* config changes are deployed as a single unit.  Also, the coolest thing of all would be the ability to *revert* the whole domain to arbitrary previous states, by simply playing the log backwards. If the differences prove too great (either in size or in age) to pull in diffs, then the whole state can always be pulled down into the SM. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/545361#545361] Start a new discussion in Management Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]