CCXML Voxeo 1.0 Development Guide

| TOC

This documentation is for CCXML 1.0-Voxeo, which has been superceded by CCXML 1.0-W3C. The CCXML-Voxeo platform is not being updated any longer. The CCXML 1.0-W3C version, however, has many new features and is actively being enhanced. If you're writing a new CCXML application, you should use CCXML 1.0-W3C. Click here for the CCXML 1.0-W3C documentation.

Introduction to CCXML Error handling

Now that we have covered event handling within the scope of CCXML, we now move on to the second most important topic, this being error handling. Let's face it, nobody writes perfect code the first time, and we are always finding that callers simply don't act as we plan in most cases, so having a solid understanding of possible CCXML errors is the key to designing a foolproof application.

When in the initial design stages of your CCXML app, you will at the very least want to have the following bit of code embedded for troubleshooting and debugging purposes:


   <transition event="error.*" name="evt">
      <log expr="'an error has occured (' + evt.error+ ')'" />
      <exit/>
    </transition>

This way, whenever our application goes haywire, we can take a peek at the Voxeo logger output to see exactly which error occured. More importantly, it prevents infinite looping within your application, so it's in your best interests as a developer to make a habit out of including this within your code.

Before we dive in and get our hands dirty with the next CCXML Lesson, we'll present a few more links to the w3c working draft so that we can study the background concepts a bit before walking into the Lesson unprepared:

Read enough background material? Lets get started learning about Errors And You!

ANNOTATIONS: EXISTING POSTS

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

Advanced Event Handling

| TOC

Error Handling