Hi Henning, On Thu, 9 Jan 2003, Henning P. Schmiedehausen wrote:
> Hm. I'm pretty sure noone really thought about this as much as you > did. The configurations package is used most of the time to provide > simple access to properties keys and there has been some work for > XML. If you can unwind all the cases for subsets, feel free to do > so. As most of the current users don't need that kind of "changing > properties on the fly via subsets", it wasn't ever implemented. > > commons-configuration is a really quiet package so if you feel that > you can contribute patches for improvements, feel free to post them > here or send them to me and Martin Poeschl (as we seem to be the only > active developers on configuration at the moment) and if they don't > break current behaviour too much, we'll put them in. > Okay. Guess I will have to spare one more of the few hours of sleep that I got left. But I will do it. Expect a patch in the end of the next week. I have quite an idea of improvements that would not change anything of the way it works for now so current users won't be missing anything. Speaking of them, do you know of projects that make use of commons-configuration yet ? I would like to see how it is actually used, and if anybody has already mentionned a missing feature (other than XML which was debated recently). One feature I would think of (other than the subsets and defaults we discussed of) is the ability to use system properties. I am not quite sure if it is possible right now (I will take a deeper look at home tonight) to get a PropertiesConfiguration object from the System.getProperties() object. I ask because I use to have system properties as the fallback of any of my configuration. Regards, Herve -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
