Recently I went back to doing Flex work and one of the things I immediately missed was ColdFire. So I decided to take a look to see what could be done to get my favorite debugging tool working with CF powered Flex applications. Turns out it wasn't all that hard. First though, check out the video below to get an idea of what I'm talking about. (Sorry, no sound as I recorded this at work.)
What the video shows is me clicking around a quick demo app I put together with the CF/Flex application generation wizard. As you can see, I now have access to all of my CF debugging info down in the ColdFire panel. So how did I do this? Easy, just include coldfire.cfm onRequestEnd. It turns out that while remote CFC calls do not include the debugging template specified in the CF administrator, the debugging service does run, so we just need to include our debugging template manually. For this example I just put coldfire.cfm in the components directory along with the following Application.cfc:
I then was able to see all my query and execution info and do trace and timer calls. The only thing that won't work is the Variables tab as everything is happening in CFCs. However, with the new enhanced tracing option I can still easily dump variables out to coldfire, as the video shows.
I haven't tested this yet, but this approach may work with other remote CFC calls, say via cfajaxproxy. If anyone tries this approach with other remote CFC calls please let me know how it works out.