[
https://issues.apache.org/jira/browse/CONFIGURATION-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-439.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.7
The fix for CONFIGURATION-437 also solved this issue.
An additional unit test was added to verify that log output created by nested
configuration builders and optional configurations is actually suppressed if
the error listeners of the original configuration builder have been cleared.
> Should be possible to disable default error log listener
> ---------------------------------------------------------
>
> Key: CONFIGURATION-439
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-439
> Project: Commons Configuration
> Issue Type: Improvement
> Components: Events & Notifications
> Affects Versions: 1.6, Nightly Builds
> Reporter: Mike Noordermeer
> Fix For: 1.7
>
>
> 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: http://www.atlassian.com/software/jira
