essary because
reloads are now detected. Is this correct?
Oliver
Am 22.03.2014 23:55, schrieb Martin Gainty:
Date: Sat, 22 Mar 2014 22:39:14 +0100
From: dont_k...@gmx.net
To: user@commons.apache.org
Subject: Re: [configuration] Calling getConfiguration on
DefaultConfigurationBuilder more than once
ont_k...@gmx.net
>> To: user@commons.apache.org
>> Subject: Re: [configuration] Calling getConfiguration on
>> DefaultConfigurationBuilder more than once permitted
>>
>> Hi Martin,
>>
>> I found a solution which fits my requirements without this ugly
>&g
rick and I want my queen back :)
Am 22.03.2014 23:55, schrieb Martin Gainty:
Date: Sat, 22 Mar 2014 22:39:14 +0100
From: dont_k...@gmx.net
To: user@commons.apache.org
Subject: Re: [configuration] Calling getConfiguration on
DefaultConfigurationBuilder more than once permitted
Hi Martin,
I
> Date: Sat, 22 Mar 2014 22:39:14 +0100
> From: dont_k...@gmx.net
> To: user@commons.apache.org
> Subject: Re: [configuration] Calling getConfiguration on
> DefaultConfigurationBuilder more than once permitted
>
> Hi Martin,
>
> I found a solution which fits m
Hi Martin,
I found a solution which fits my requirements without this ugly
behaviour as described before. The trick is to configure the reloading
strategy and force the reload checking in "config.xml":
config-class="org.apache.commons.configuration.reloading.FileChangedRe
> Date: Fri, 21 Mar 2014 22:45:29 +0100
> From: dont_k...@gmx.net
> To: user@commons.apache.org
> Subject: [configuration] Calling getConfiguration on
> DefaultConfigurationBuilder more than once permitted
>
> Hi,
>
> is it permitted to call getConfiguration more than once on the same
> i
