[
https://issues.apache.org/jira/browse/ACE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213131#comment-13213131
]
Marcel Offermans commented on ACE-216:
--------------------------------------
Let's start with the bad news. I recently updated autoconf, and after
re-reading the spec had to move applying the configuration data to the commit()
phase. The bad news is that commit() cannot fail, so any errors there will
still only be logged. However, while parsing the files I think we can do a
better job (maybe already server side).
> Better error reporting with metatype/autoconf configuration file issues
> -----------------------------------------------------------------------
>
> Key: ACE-216
> URL: https://issues.apache.org/jira/browse/ACE-216
> Project: ACE
> Issue Type: Improvement
> Reporter: Paul Bakker
>
> If a metatype file is invalid (typo in a attribute name for example) the
> deployment will fail. No useful error is reported back to ACE. The only way
> to debug this is to first deploy a console and LogService, and then deploy
> the configuration files. The errors will show up in the LogService on the
> target, but this means you need access to the target.
> An error message in the log on the ACE service such as "deployment failed
> because of an undefined parameter 'abc' in file myconfig.xml" would be most
> helpful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
