[jboss-jira] [JBoss JIRA] Updated: (JBAS-8680) More robust handling of previous versions of the configuration files

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/JBAS-8680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated JBAS-8680:
-----------------------------------

    Fix Version/s: 7.0.0.Beta3
                       (was: 7.0.0.CR1)


> More robust handling of previous versions of the configuration files
> --------------------------------------------------------------------
>
>                 Key: JBAS-8680
>                 URL: https://issues.jboss.org/browse/JBAS-8680
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Brian Stansberry
>             Fix For: 7.0.0.Beta3
>
>
> Currently when an update is made to the configuration, we copy the config file to ".lastknowngood" and write a new version. We need something more sophisticated than that.
> 1) The original version of present on server start should be saved as .original.
> 2) We should keep a proper versioned history (standalone.xml.v1, standalone.xml.v2 etc)
> 3) Keep a standalone.xml.last which is the same as the current standalone.xml. This can be used to detect (via file timestamps) changes to standalone.xml made while the server is offline -- such change results in a new .original.
> 4) We need to create proper semantics for the ".lastknowngood" notion, or scrap it. Right now it's just the previous version of the file, which may or may not have been "good".

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira