I catch all server-side exceptions on the server, and write them into the xml I return to the client. The client resulthandler looks at the xml to determine if it is good data or an error and responds appropriately. For the few occasions where the server app itself errors, I use a fault handler.
The problem with faultString is that if the server errors with a 500, the browser does not pass the full error informtion to the player. It is possible to cause the server to send a 200 instead of a 500, and you can then access the fault detail. How this is done depends on the server. Tracy ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Valy Sivec Sent: Friday, January 12, 2007 3:44 PM To: [email protected] Subject: [flexcoders] How to handle server side errors on the UI Hello flexcoders, I'm working on a project that uses HTTP services and I'm having difficulties catching the server side error on the client. In fact, I'd like to be able translate the error code from the back-end to a meaningfull message to the client for certain error codes. It looks that faultString doesn't help me much. How do you guys deal with the server side errors on the client, if you want to have custom error messages depending on the error code? Thanks, Valy Sivec ________________________________ Any questions? Get answers on any topic at Yahoo! Answers <http://answers.yahoo.com/;_ylc=X3oDMTFvbGNhMGE3BF9TAzM5NjU0NTEwOARfcwMz OTY1NDUxMDMEc2VjA21haWxfdGFnbGluZQRzbGsDbWFpbF90YWcx> . Try it now.
