I envision making a lot of property changes in a test environment and then in one swoop loading them all into production. We don't want our production environment to start accessing properties until all the properties are loaded. It seems that with conditional elements and XML injection that we could do this. What I'm wondering is if this technique has been specifically addressed in the documentation or if there are thoughts as to how to do this. The same would be true of rolling back a production change to a previous set of properties. It seems simple enough that you could have one variable that holds the property set 'version'. Then you have conditional elements that check the version, if this version then this property applies, etc. Then with one transaction you change the version number. Would this be a way to do it? Thoughts?
Posts:
1
Registered:
Mar 31, 2007 10:05:44 PM
Re: Testing and then submitting XML into production all at once
Posted:
Mar 31, 2007 10:12:21 PM
in response to: 's post
I'm not sure if I fully understand the nature of your question. Typically, all of the properties are in a XML file. None of the properties would become available before any other when the file is loaded or updated. On a production update, the XML file would be read and only when all initialization is complete does it replace the existing set already in memory.
