[
https://issues.apache.org/jira/browse/CONFIGURATION-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088256#comment-13088256
]
Oliver Heger commented on CONFIGURATION-397:
--------------------------------------------
What is the status of this issue? I see that there have been multiple commits.
Is the problem solved or is there some work left?
> Schema validation exceptions in a combined configuration often result in an
> empty configuration being include with no exception or error message.
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONFIGURATION-397
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-397
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.7
> Environment: Linux, JBoss, JDK 6
> Reporter: Ralph Goers
> Assignee: Ralph Goers
> Fix For: 1.7
>
>
> When using DefaultConfigurationBuilder to construct a combined configuration
> using MultiFileHierarchicalConfiguration (the override file) followed by
> XMLConfiguration (the default file), if one of the override files has a
> schema validation error the exception is not thrown nor is an error logged.
> Instead, an empty configuration is returned.
> If schema violation exceptions occur they should always throw exceptions,
> regardless of whether a file is optional or not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
