> The fact is that for *production* the one file is good. This is your assumption... not always the case... actuall should not matter too much if the folks running thr show know what they are doing. Further more the many file config now can be turned into a single file config if desired.
I think this is a very weak argument. > I repeat that this discussion is premature. At this point we are running > on > empty when it comes to user feedback as the limits of the current system > are > not known by the users we are guessing based on our abilities, this always > fails. Yes, glad to hear toy say this. BTW, if we abstract the configuration completly into an isolated service which deals with an config API model, then we can implement any fashion of configuration... single file, multi file, database whatever. Then let the user pick what the end method of persistence is. --jason ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
