Mailing-List: contact commits-help@ace.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ace.apache.org
Date: Tue, 21 Feb 2012 23:02:48 +0000 (UTC)
From: "Paul Bakker (Created) (JIRA)" <jira@apache.org>
To: commits@ace.apache.org
Message-ID: 
 <1163629210.1661.1329865368815.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (ACE-216) Better error reporting with
 metatype/autoconf configuration file issues
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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