Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <50DA0C1C.4060107@oliver-heger.de>
Date: Tue, 25 Dec 2012 21:27:08 +0100
From: Oliver Heger <oliver.heger@oliver-heger.de>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: [configuration] Defining variable resolvers in configuration
 definition
 files
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

currently I am working on [CONFIGURATION-518] - rework of interpolation 
features.

DefaultConfigurationBuilder supports that custom variable resolvers can 
be defined in its definition files. I noticed that these resolvers are 
not only used locally, but are also registered as global lookup objects. 
I think, this behavior is pretty invasive, and it does not seem to be 
documented (at least not in the Javadocs of 
DefaultConfigurationBuilder). This seems to be a workaround for making 
such custom resolvers available to other objects (e.g. 
ConfigurationInterpolator objects in DynamicCombinedConfiguration).

I temporarily disabled this mechanism (and had to @Ignore 4 test cases 
which now are failing). I hope to find a better solution based on the 
builders approach I am working on in parallel. In this context, I also 
plan to have a more generic mechanism to define default settings for 
newly created Configuration objects.

Oliver

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