Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 35134 invoked from network); 16 Feb 2004 19:57:36 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 16 Feb 2004 19:57:36 -0000 Received: (qmail 32755 invoked by uid 500); 16 Feb 2004 19:57:12 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 32711 invoked by uid 500); 16 Feb 2004 19:57:12 -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 24147 invoked from network); 16 Feb 2004 16:00:08 -0000 Date: Mon, 16 Feb 2004 17:00:03 +0100 (MET) From: Christian Siefkes X-X-Sender: siefkes@elch.inf.fu-berlin.de Reply-To: Christian Siefkes To: Eric Pugh cc: 'Jakarta Commons Developers List' Subject: RE: [configuration] Refactor AbstractConfiguration(Configuration defaults) In-Reply-To: <004d01c3f49b$f6a85100$657ba8c0@IQUITOS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Envelope-Sender: siefkes@mi.fu-berlin.de X-Virus-Scanned: by AMaViS 0.3.12pre7-F28[11872](NAI-uvscan@mi.fu-berlin.de) X-Remote-IP: 160.45.110.124 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi, On Mon, 16 Feb 2004, Eric Pugh wrote: > True.. But, you could grab the propertiesConfiguration out of the composite > and save it.. I think the composite should be looked at as a read only > "thing" because saving has too many odd ramifications.. > > And, at least, the one user who mentioned the > AbstractConfiguration(Configuration conf) is actually using a > CompositeConfig anyway, and needs that exact same problem solved.. Well, as long as CompositeConfigs are read-only/in-memory-only, I don't think they can fully substitute chainable defaults. But of course, adding a save() method to CompositeConfig doesn't make sense, because they don't have a native format. Maybe a CompositeConfiguration.flatten(Configuration out) method that adds all key/value pairs to the "out" configuration? This would allow flattening a Composite to BaseProperties or XML/DOM4J or any other format and storing the flattened configuration... Bye Christian PS. Please cc me as I'm not on the list. ------------ Christian Siefkes ----------------------------------------- | Email: christian@siefkes.net | Web: http://www.siefkes.net/ | Graduate School in Distributed IS: http://www.wiwi.hu-berlin.de/gkvi/ -------------------- Offline P2P: http://www.leihnetzwerk.de/ ---------- More than any time in history, mankind now faces a crossroads. One path leads to despair and utter hopelessness, the other to total extinction. Let us pray that we have the wisdom to choose correctly. -- Woody Allen --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org