ingle instance of Configuration which
automatically reflects the changed properties.
Unluckily the example with ten same property files was bad. In my real use case
I use references to ten different property files.
Stefan
Hi,
Am 23.03.2014 18:17, schrieb dont_know:
Hi Martin,
I hope you haven
Hi Martin,
I hope you haven't missunderstood me: the behaviour of
DefaultConfigurationBuilder is ugly, not your solution ;)
But I think you have overlooked the second important part in the
config.xml -> the definition of a ReloadStrategy for the referenced
properties. This did the trick and
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
Hi,
is it permitted to call getConfiguration more than once on the same
instance of DefaultConfigurationBuilder like this:
DefaultConfigurationBuilder builder = new DefaultConfigurationBuilder();
builder.setFile(new File("config.xml"));
Configuration config = builder.getConfiguration(true);
co
