I have been building an exception handling framework and doing some experimenting with this myself. Currently my focus is structured exception handling for CFCs(throwing and logging, as well as tracing and dumping while debugging), but integrating this with Flash is definitely on the radar. I'd say I'm about a week away from having a usable framework, then I'd like to look at the Flash side.
Right now, I only know of one way to propagate exceptions up to Flash, and that is returning error text via the "Flash.Result" param. I haven't looked too far into it though (like at all), so if anybody knows a better way or has done any work with this I'd love to hear about it as well. I'll be documenting and releasing the framework eventually, but if you'd like some advance details on it, feel free to email me directly at [EMAIL PROTECTED] -----Original Message----- I'm interested in implementing global error trapping and reporting in my Flash Remoting/CFC-based application. Has anyone experimented with this or have opinions on the best approach? I'd like to come up with a cleaner methology than wrapping all the code inside each CFC method with try/catch blocks, if that is possible. -- Scott Keene [EMAIL PROTECTED] ---------------------------------- CFOOP - Object Oriented ColdFusion http://www.cfoop.com -- ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
