If the AsyncToken is null then either an error occurred before the invocation could even be sent to the server... or that the response was not a well formed implementation of mx.messaging.messages.AcknowledgeMessage and thus could not correlate the result or fault with an outstanding request and hence could not locate a token. Can you check the Channel endpoint is actually active? If you're not contacting an FDS capable endpoint (such as FDS or CF) are you sure that implementation is returning strongly typed AS3 messages? Pete
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Allman Sent: Thursday, May 10, 2007 5:25 PM To: [email protected] Subject: RE: [flexcoders] Re: rpc fault handler not called Unfortunately that runs into another problem I'm having. When I put a fault handler on the RemoteObject or Operation, it gets called but the token property of the FaultEvent is null. Hmmm??? So I can't access the token associated with the call. Any idea why that's happening? According to the docs on AsyncToken, it's supposed to be attached to FaultEvents. Thanks. Michael On Thu, 10 May 2007, Tracy Spratt wrote: > I am just suggesting that you simplify the conditions by not using a > responder function. Instead, just put a string in the AsyncToken, and > use a hard coded fault handler. > > > > Tracy > > > > ________________________________ > >> From: [email protected] <mailto:flexcoders%40yahoogroups.com> [mailto:[email protected] <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of Michael Allman > Sent: Thursday, May 10, 2007 4:47 PM > To: [email protected] <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Re: rpc fault handler not called > > > > I did not receive my message, so I'm responding to my original post. > > This is actually in response to Tracy Spratt's message. > > What is the ACT token? And the responder's fault handler is simply not > called. I've debugged it to no avail. I need to see the source to > mx.rpc stuff in order to understand what's going on. Unfortunately, that > > appears to be under wraps. > > Thanks for your help. > > Michael > > On Thu, 10 May 2007, Michael Allman wrote: > >> Hi, >> >> Can anyone tell me how to get Flex to call a fault handler associated > with >> an rpc call? This is the pattern I'm using: >> >> var token:AsyncToken = operation.send(); >> token.addResponder(responder); >> >> However, my responder's fault method is never called. Instead I get an >> error message from flash player with a strack trace that looks like >> >> > mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faul <http://www.adobe.com/2006/flex/mx/internal::faul> > tHan <http://www.adobe.com/2006/flex/mx/internal::faultHan <http://www.adobe.com/2006/flex/mx/internal::faultHan> > >> dler() >> at mx.rpc::Responder/fault() >> at mx.rpc::AsyncRequest/fault() >> at >> > ::NetConnectionMessageResponder/NetConnectionChannel.as$40:NetConnection > Mess >> ageResponder::statusHandler() >> at mx.messaging::MessageResponder/status() >> >> whenever I receive a fault. >> >> Thanks a bunch! >> >> Michael >> > > > >
