Return-Path: 
 <commons-user-return-15008-apmail-jakarta-commons-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org
Received: (qmail 68851 invoked from network); 26 Jan 2006 09:14:03 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 26 Jan 2006 09:14:03 -0000
Received: (qmail 11034 invoked by uid 500); 26 Jan 2006 09:13:58 -0000
Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org
Received: (qmail 10831 invoked by uid 500); 26 Jan 2006 09:13:57 -0000
Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-user-unsubscribe@jakarta.apache.org>
List-Help: <mailto:commons-user-help@jakarta.apache.org>
List-Post: <mailto:commons-user@jakarta.apache.org>
List-Id: "Jakarta Commons Users List" <commons-user.jakarta.apache.org>
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Delivered-To: mailing list commons-user@jakarta.apache.org
Received: (qmail 10819 invoked by uid 99); 26 Jan 2006 09:13:56 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jan 2006 01:13:56 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=UNPARSEABLE_RELAY
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [134.98.65.18] (HELO gateway.elsag.de) (134.98.65.18)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jan 2006 01:13:55 -0800
Received: from vwall.elsag.de by gateway.elsag.de
          via smtpd (for asf.osuosl.org [140.211.166.49]) with ESMTP;
 Thu, 26 Jan 2006 10:13:33 +0100
Received: from esmail ([192.168.2.88]) by vwall-vs.elsag.de with InterScan
 Messaging Security Suite; Thu, 26 Jan 2006 10:13:32 +0100
Received: from esmail by esmail
          via smtpd (for vwall.elsag.de [192.168.100.108]) with ESMTP;
 Thu, 26 Jan 2006 10:13:32 +0100
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Subject: RE: [Configuration] Wish list
Date: Thu, 26 Jan 2006 10:13:32 +0100
Message-ID: <F0D7281DAB048B438E8F5EC4ECEFBDDC7D7BAA@esmail.elsag.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Configuration] Wish list
Thread-Index: AcYiUZLJiQCpzgx2QvmJ70G337cdtAAA5YXA
From: =?iso-8859-1?Q?J=F6rg_Schaible?= <Joerg.Schaible@Elsag-Solutions.com>
To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hi Borut,

Borut Bolcina wrote on Thursday, January 26, 2006 9:21 AM:

[snip]

> *[1] Getting Properties out of Configuration*
> When using already written software components, some methods take
> Properties as input parameter. If using CompositeConfiguration as a
> central point for accesing properties, it would be desirable to get
> Properties out of PropertiesConfiguration which is part of
> CompositeConfiguration. Example of wanted functionality:
>=20
> Configuration propertiesConfiguration =3D config.getConfiguration(2);
> Properties properties =3D propertiesConfiguration.getProperties();
>=20
> Asume 3rd entry in configuration.xml is <properties>.

It is here and it is not tied to a spcific Configuration implementation:
ConfigurationConverter.getProperties(Configuration)

Hint for docu:
http://jakarta.apache.org/commons/configuration/overview.html
Should mension, that it does convert vice versa :)

[snip]

> *[3] Getting configurations out of configuration.xml could be done by
> name and not by index.* So, instead of
> config.getConfiguration(2)
> one could write
> config.getConfiguration("entryThree");
>=20
> A new attribute for each entry should be introduced, something like:
>   <configuration>
>	 <xml id=3D"entryOne" fileName=3D"prop1.xml"/>
> 	 <xml id=3D"entryTwo" fileName=3D"prop2.xml"/>
>	 <properties id=3D"entryThree" fileName=3D"prop3.properties"/> =20
> 	 <database id=3D"entryFour"
> connect=3D"jdbc:mysql://delovc10.noviforum.si/feeds?user=3Dfoo&pas
> sword=3Dbar"/>
>   </configuration>=20

Since you make seem to access the distinct configuration files anyway, =
use subsets instead:

<configuration>
    <additional>
        <xml fileName=3D"prop1.xml" at=3D"prop1" at=3D"entryOne" />
        <!-- ... -->
    </additional>
</configuration>

config.subset("entryOne");

- J=F6rg

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org