I am using the latest commons config on JDK1.6. Is there a way
to suppress exceptions pertaining to missing optional property files?
Thanks,
/Ur
Configuration:
Exception:
Caused by: org.apache.commons.configuration.ConfigurationException: Cannot
locate configuration source /home/jdo
Try using ConfigurationBuilder instead of ConfigurationFactory, you
shouldn't have this exception.
Emmanuel Bourg
[EMAIL PROTECTED] a écrit :
I am using the latest commons config on JDK1.6. Is there a way
to suppress exceptions pertaining to missing optional property files?
Thanks,
/Ur
Con
On Apr 6, 2008, at 4:42 PM, Emmanuel Bourg wrote:
Try using ConfigurationBuilder instead of ConfigurationFactory, you
shouldn't have this exception.
I get it with the following:
try {
DefaultConfigurationBuilder builder = new
DefaultConfigurationBuilder();
builder.setURL(confi
Gavin Eadie schrieb:
On Apr 6, 2008, at 4:42 PM, Emmanuel Bourg wrote:
Try using ConfigurationBuilder instead of ConfigurationFactory, you
shouldn't have this exception.
I get it with the following:
try {
DefaultConfigurationBuilder builder = new
DefaultConfigurationBuilder();
That makes perfect sense, and is a nice design -- thanks for the
explanation .. Gavin
_
On Apr 8, 2008, at 8:51 PM, Oliver Heger wrote:
If a configuration marked as optional cannot be loaded,
DefaultConfigurationBuilder notifies all registered error listeners
ConfigurationBuilder yields CombinedConfiguration.
I have so far based my stuff on CompositeConfiguration.
I do not see a type relationship (is-a) between the two.
How do we migrate from CompositeConfiguration to
CombinedConfiguration?
What are the risks?
Regards
/Ur
-- Original m
[EMAIL PROTECTED] wrote:
> ConfigurationBuilder yields CombinedConfiguration.
> I have so far based my stuff on CompositeConfiguration.
> I do not see a type relationship (is-a) between the two.
> How do we migrate from CompositeConfiguration to
> CombinedConfiguration?
>
> What are the risks?
>
