[jira] Commented: (CONFIGURATION-285) configuration fileName=local-configuration.xml config-optional=true / 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_12514493 ] Thorbjørn Ravn Andersen commented on CONFIGURATION-285: --- Thank you for adding this extension. I still believe that invalid subconfigurations should be treated differently from optional, non-existant subconfigurations regardless of the invalidation cause, and that the silent ignoring should be a switch that needs to be set, similarly to the config-optional attribute. I.e. if an optional subconfiguration is invalid, a configuration exception should be thrown. I'd prefer not to use CVS-snapshots in production code - do you have a rough estimate of when 1.5 will be released? 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 Assignee: Oliver Heger Fix For: 1.5 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONFIGURATION-285) configuration fileName=local-configuration.xml config-optional=true / 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_12514507 ] Oliver Heger commented on CONFIGURATION-285: I follow your argumentation in principle, but I don't see an easy (and generic) way to find out when a subconfiguration is invalid. So the idea with the event listener approach is to provide a way for implementing this decision yourself. ATM there are no concrete plans for a 1.5 release yet. There are still some JIRA tickets, which need to be addressed. So, unfortunately, I really cannot anticipate a release date. 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 Assignee: Oliver Heger Fix For: 1.5 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONFIGURATION-285) configuration fileName=local-configuration.xml config-optional=true / 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]