ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (ACE-216) Better error reporting with metatype/autoconf configuration file issues
Date Tue, 05 Nov 2013 09:30:20 GMT

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

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

    Resolution: Fixed

We now report an error if a resource processor is missing, but for the rest there is very
little we can do beyond reporting the error when it occurs.

> 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
>
> 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.1#6144)

Mime
View raw message