That's correct. This is a well known issue. The problem is that certain browser won't allow the plugin to access the returned content when the http status code is 500 - a requirement for web service faults. You can work around this by suppressing the 500 and changing it to a 200. What are your web services implemented in? If Java, I can send some classes and web.xml config to work around this changing the http status code to 200 only when invoked by the flash player. Carson ____________________________________________ Carson Hager Cynergy Systems, Inc. http://www.cynergysystems.com <http://www.cynergysystems.com/> Email: [EMAIL PROTECTED] Office: 866-CYNERGY Mobile: 1.703.489.6466
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Pablo Apanasionek Sent: Friday, November 10, 2006 7:56 AM To: [email protected] Subject: [flexcoders] Webservices fault message when not using proxy I've checked the livedocs regarding fault events on WebService calls, but I haven't found anything regarding this: When not using the proxy (useProxy=false), the fault message raised by the server seem to be choked by a black hole while returning to the SWF file, making it impossible to show a friendly message to the user if an exception (whether system or business) comes up in the middle. I've debugged the request/response and the error is coming back correctly, but the SWF seems to dismiss it. This doesn't happen when using the proxy. Did I miss any docs or something? TIA, -Pablo Gustavo Apanasionek
