commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Noordermeer (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-439) Should be possible to disable default error log listener
Date Sat, 05 Mar 2011 16:38:45 GMT


Mike Noordermeer commented on CONFIGURATION-439:

Could be, but maybe you do want to log errors other than non-existent optional configurations
(imho it's weird that gets logged as an error anyway).

But I think the fundamental problem is in the fact that most settings don't seem to be inherited
by child DefaultConfigurationBuilders. IMO, you would expect the child builders (and maybe
even the configurations) to inherit settings like the error and change listeners, but also
things like setDelimiterParsingDisabled().

> Should be possible to disable default error log listener 
> ---------------------------------------------------------
>                 Key: CONFIGURATION-439
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Improvement
>          Components: Events & Notifications
>    Affects Versions: 1.6, Nightly Builds
>            Reporter: Mike Noordermeer
> The current version of Commons Configuration always adds a default error listener that
logs internal errors. This causes an exception to be logged when, for instance, an optional
include from a DefaultConfigurationBuilder is not found. The default error listener can be
removed with clearErrorListeners(), but this is not easily possible when recursively including
a DefaultConfigurationBuilder config in a DefaultConfigurationBuilder config.
> It should be possible to disable the default logging of internal errors, or at least
disable the default logging of non-existent optional configuration files.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message