You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@ace.apache.org by "Marcel Offermans (JIRA)" <ji...@apache.org> on 2014/04/17 10:57:14 UTC

[jira] [Closed] (ACE-216) Better error reporting with metatype/autoconf configuration file issues

     [ https://issues.apache.org/jira/browse/ACE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Offermans closed ACE-216.
--------------------------------

    Resolution: Fixed

Closed all issues I just reopened and targeted for 'next' release.

> 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
>          Components: Architecture
>            Reporter: Paul Bakker
>            Assignee: Marcel Offermans
>             Fix For: next
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)