Has any thought been given to incorporating jelly or something similar into the processing of the configuration files? My main line of thinking on this is how maven uses jelly to process the project.xml file and to replace values in the pom with those declared in a properties file. As applications get larger with many components and the possibility of multiple configuration files the administration and configuration of these applications can become quite confusing and overwhelming for the end user who is responsible for these tasks. It also appears that , at least form my point of veiw anyway, that the configuration of an application changes very little and only small changes are made to set it up in a given environment. These changes are things like the ports for sockets to listen on and the like. I understand that there are overrides but I'm not sure that this creates the ease of use that a simple properties file can for end users.
Using jelly as a preprocessor could open up many other possibilities as well.
Rob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
