You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2007/07/11 22:22:04 UTC
[jira] Commented: (CONFIGURATION-285) does not
report parsing errors in local-configuration.xml
[ https://issues.apache.org/jira/browse/CONFIGURATION-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511852 ]
Oliver Heger commented on CONFIGURATION-285:
--------------------------------------------
Just to make sure I understand your request correctly: If the config-optional attribute is set to true and loading this sub configuration causes an error, the exception should be logged. Other behavior need not be changed, correct?
> <configuration fileName="local-configuration.xml" config-optional="true" /> does not report parsing errors in local-configuration.xml
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONFIGURATION-285
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-285
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Thorbjørn Ravn Andersen
>
> I'm trying to build a configuration system to be shared between our Java applications. I therefore want to have optional configurations included from the main configuration file read by DefaultConfigurationBuilder
> <configuration fileName="local-configuration.xml" config-optional="true" />
> I have found that if the sub-configuration file is invalid the error is silently ignored. The same without config-options="true" results in a ConfigurationException to be thrown (which wraps a ConfigurationRuntimeException which wraps the ConfigurationException which wraps the SAXException).
> I believe that the behaviour is incorrect. The sub-configuration file should be skipped if not found, but any errors found when parsing the existing file should be logged.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org