Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 55003 invoked from network); 9 Jan 2003 17:23:18 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 9 Jan 2003 17:23:17 -0000 Received: (qmail 3874 invoked by uid 97); 9 Jan 2003 17:24:32 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 3841 invoked by uid 97); 9 Jan 2003 17:24:31 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 29031 invoked by uid 98); 9 Jan 2003 16:50:15 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) To: commons-dev@jakarta.apache.org Path: forge.intermeta.de!not-for-mail From: "Henning P. Schmiedehausen" Newsgroups: hometree.jakarta.commons.dev Subject: Re: [configuration] My thoughts on subsets and defaults Date: Thu, 9 Jan 2003 16:48:50 +0000 (UTC) Organization: INTERMETA - Gesellschaft fuer Mehrwertdienste mbH Lines: 47 Sender: henning@forge.intermeta.de Message-ID: References: <20030109151915.G36236@puget.esil.univ-mrs.fr> Reply-To: hps@intermeta.de NNTP-Posting-Host: forge.intermeta.de X-Trace: tangens.hometree.net 1042130930 21695 212.34.181.4 (9 Jan 2003 16:48:50 GMT) X-Complaints-To: news@intermeta.de NNTP-Posting-Date: Thu, 9 Jan 2003 16:48:50 +0000 (UTC) X-Copyright: (C) 1996-2002 Henning Schmiedehausen X-Newsreader: NN version 6.5.1 (NOV) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Herve Quiroz writes: >Hi all, ReHi, > * First, the defaults. Why is it a protected field in BaseConfiguration ? Well. Because the first one to write this code did it like this? If you think, this should be changed, send me a patch. I'll review it and if it does not change user visible behaviour (at least not too much :-) then I'll put it in. >I mean why don't you have the following in the Configuration interface: > Configuration.setDefaults(Configuration defaults) >So a Configuration object (here defaults) could act as the "fallback" for >another one. This might lead to your second point: Shall the new Object just "proxy" the settings of the default or should it copy them? [... more on proxying and subsets ...] 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. Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de D-91054 Buckenhof Fax.: 09131 / 50654-20 -- To unsubscribe, e-mail: For additional commands, e-mail: