CallXML 2.0 Development Guide

| TOC

This documentation is for CallXML 2, which has been superceded by CallXML 3. The CallXML 2 language is not being updated any longer. CallXML 3, however, has many new features and is actively being enhanced. If you're writing a new CallXML application, you should use CallXML 3. Click here for the CallXML 3.0 documentation.

Appendix E: Exceptions & Errors Explained

Knowing that you have an error is the first step to a solution. But, in order to get closure on our error issues, we also need to know exactly what errors can get thrown in the CallXML environment, exactly what they mean, and how to interpret them when they happen. In this appendix, you will find a bevy of useful knowledge pertaining what errors and exceptions can happen in particular coding circumstances. We will also go over techniques for trapping and handling the exceptions that are bound to crop up during the average development cycle of an application. The topics covered in this section are as follows:

Overview

General Debugging Techniques: This subsection contains advice on how to write and debug a trouble-free CallXML application. This section also offers a linear, step-by-step guide for troubleshooting your application when your code seems to be riddled with errors.

The Voxeo Real Time Logger: This section explains the intricacies of using the Voxeo real-time logging tool to help troubleshoot your application. Topics covered include a logger how-to guide, logger features, and how to discern an error from a system message.

Getting Support Help: The information contained within this portion of the appendices offers advice on how to get the quickest, most accurate response to support when you simply can't figure out the error on your own. Details include where to send your problems, what we will need to help you, and good old-fashioned, down-home humor to tide you over while you wait for us to fix your application.

Logger Key -- CallXML: This subsection contains the information that you will need to interpret each cryptic logger message that you might encounter, as well as helpful suggestions on how to track down the error so that the logger will quit outputting those pesky error messages.

ANNOTATIONS: EXISTING POSTS

0 posts - click the button below to add a note to this page

D: Best Practices

| TOC

| General Debugging Techniques