I have been working on several examples of using ColdFusion with AJAX. Twice already I have received strange errors about the XML being malformed after I had it working just fine. Both times after debugging I realized that the error was related to the ColdFusion debugging info that was outputting at the bottom of the screen. ARGH!!

Now I am doing two simple things that make life much easier.

1. Explicitly disabling debugging on that page.

<code><cfsetting showdebugoutput=”false” /></code>

2. Simply use the docked version of the CF debugger.

After looking at some already available CFCs that Sean told me about, I decided to customize something I already had. Take a look:

http://www.resonantmedia.com/downloads/public/envoy/envoy.zip

Basically I had a factory pattern based service message cfc (or set of
CFCs) that handled the messages for one of my applications. It worked very well. I had the “dictionary” stored in different “handler” cfcs.
After seeing the dictionary xml docs that Joe and Doug use I decided to use that instead.

The reason I created “Envoy” (that is what I am calling it for lack of a better name) is because both Reactor and MG have error messaging dictionaries, but I wanted something to manage all messages regardless of type and regardless of framework. IT also supports multiple languages (i.e Spanish and English). If no language is passed in English is assumed.

It may not be useful to anyone but me, but let me know what you think. I am sure there are things that could be improved.