[ http://issues.apache.org/jira/browse/GERONIMO-1951?page=comments#action_12377854 ]
Aaron Mulder commented on GERONIMO-1951: ---------------------------------------- Now PersistentConfigurationList has methods to identify all Artifacts that it has data on matching an Artifact pattern, and to migrate the config settings from an old configuration name to a newer configuration name. We just need to change the deployment process to use these. > config.xml settings should be applied to newer versions > ------------------------------------------------------- > > Key: GERONIMO-1951 > URL: http://issues.apache.org/jira/browse/GERONIMO-1951 > Project: Geronimo > Type: Bug > Security: public(Regular issues) > Components: kernel > Versions: 1.1 > Reporter: Aaron Mulder > Priority: Blocker > Fix For: 1.1 > > If you deploy a module with no version number, it gets one during deployment > and any config.xml settings are written using that version number. Then if > you redeploy, the app gets a newer version, and a new entry is written to > config.xml. It should transfer the old settings to the new configuration > (checking to make sure each is still valid) rather than writing a whole new > configuration block. > The same is true if you deploy an updated version of a core Geronimo service, > e.g. updating geronimo/jetty/1.1.2/car to geronimo/jetty/1.1.3/car -- it > should not forget any custom ports assigned, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
