Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <41B02ED3.9030606@lfjr.net>
Date: Fri, 03 Dec 2004 10:16:03 +0100
From: Emmanuel Bourg <smanux@lfjr.net>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [configuration] getProperty vs getPropertyDirect
References: <41AF5604.3030807@lfjr.net> <41B01264.7030104@med.uni-marburg.de>
In-Reply-To: <41B01264.7030104@med.uni-marburg.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sorry Olivier I should have waited a bit more before comiting the change 
:/ I have no problem reintroducing getPropertyDirect at a later time if 
you find an interesting use case.

Emmanuel Bourg


Oliver Heger wrote:
> After seeing the commit mails I may be a bit late.
> 
> I had some ideas about extending the interpolation mechanism to support 
> other data types than string, too. For this use case the separation of 
> getProperty() and getPropertyDirect() would be nice, as getProperty() 
> being a generic hook that allows for manipulation of properties (like 
> interpolation) before they are delivered to the caller.
> 
> But this was nothing concrete yet.
> 
> Oliver

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