It works!
To make real fault codes available in Flex 2.0 (RTM) from .NET
web services put the following code (C#) in your
Global.asax
void Application_PreSendRequestHeaders(object sender, EventArgs
e) From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Tuppeny Sent: Monday, July 10, 2006 1:17 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: ACcess SOAP fault code Cool, let us know how you get on. Might save me some time
when I need to "fix" it :-) From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Carson Hager Sent: 03 July 2006 15:41 To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: ACcess SOAP fault code If you swap the status code, the fault handler will still
be triggered and this time you will get the full fault. That being said, I
haven't tried this in the GA version of Flex 2. I'll be trying it this
week.
Carson
____________________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Tuppeny Sent: Thursday, June 22, 2006 12:52 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: ACcess SOAP fault code
So if we swap the 500 status code for a 200, the fault
handler won't be triggered?
This is sounding more and more useless each day! I guess
the only way to do it is with try/catch and return our own object, and
interrogate it after every call :-( From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Carson Hager Sent: 21 June 2006 13:13 To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: ACcess SOAP fault code The way it should work is for the fault handler to be
triggered due to the fact that a SOAP fault was returned. At this point, the 500
status code is what's triggering the fault.
Carson
____________________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Tuppeny Sent: Wednesday, June 21, 2006 4:05 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: ACcess SOAP fault code
[Inbound Mail Scanned by MessageLabs] ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ [Inbound Mail Scanned by MessageLabs] ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ __._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- RE: [flexcoders] Re: ACcess SOAP fault code Kelly Birr
- RE: [flexcoders] Re: ACcess SOAP fault code Kelly Birr
- Re: [flexcoders] Re: ACcess SOAP fault code Carson Hager
- RE: [flexcoders] Re: ACcess SOAP fault code Daniel Tuppeny
- [flexcoders] Re: ACcess SOAP fault code ting_first
- RE: [flexcoders] Re: ACcess SOAP fault code Carson Hager
- RE: [flexcoders] Re: ACcess SOAP fault code Carson Hager
- [flexcoders] Re: ACcess SOAP fault code ting_first
- RE: [flexcoders] Re: ACcess SOAP fault code Carson Hager