I have some issues where same configuration information is scattered into many different configuration files.
I sort of now how to solve it at deploy time but I would like if Operations only had one place to change vital information.
One way to do this, would be some sort of runtime macrosubstituions. For instance
$(ENV_VARIABLE)For substituting a value with the value from the environment variables
$(INCLUDE_FILE)For including another file
$(PROPERTY_FILE_KEY)Like (N)ANT: Refer to a value in a property file
I order to do this I need to be able to hook into the configuration XML nodes when they are loaded. I could probably do this in configuration section handlers, but I would like something generic.
And of course: If anyone has created already, that would just be swell :)
Best regards
Soeren D.
