> I'll have to play around with their suggested > workaround and see if there's any way I can get that to work, as it's > the one stumbling block for me with going this route. >
That suggested workaround is a joke, no way I'd do the massive amount of recoding needed to use that. Their suggestion is to catch any errors and append the message to your return variables. Even if that worked in my framework (which is doesn't) it would require pretty much recoding all the business logic to look for these special error messages and handle them (before any other processing is done). I'm not even sure there's a way I could handle any unexpected exceptions this way, but it certainly wouldn't be easy and would probably mean dumping the entire Flex framework to do so. It's not even close to a reasonable solution. So looks like using onCFCRequest is out of the realm of possibilities. MJS ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:343066 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
