--- In flexcoders@yahoogroups.com, "Amy" <amyblankens...@...> wrote: > I always use mx.rpc.Responder instead of AsyncResponder (is that a custom > class?). There's a working example of using AsyncToken with AMFPHP here > http://flexdiary.blogspot.com/2009/01/lazy-loading-tree-example-file-posted.html > . Maybe that will help you see something the docs aren't showing you.
Thanks for the tip, Amy, but it doesn't look any different than what I have. Additionally, I didnt see any change in behavior from SDK 3.1 to SDK 3.5. Intentionally brief, here: import mx.rpc.AsyncToken; import mx.rpc.AsyncResponder; var token:AsyncToken = myService.disableStatistics(user,pass,email,tArray); token.info = email; token.addResponder(new AsyncResponder(myResults,myFaults,token)); private function myResults(event:Object, token:AsyncToken):void { var resultEvent:ResultEvent = ResultEvent(event); } private function myFaults(event:Object, token:AsyncToken):void { var faultEvent:FaultEvent = FaultEvent(event); } disableStatistics is called, and executes correctly. I see the reply coming back in but neither myResults nor myFaults is ever called. If I add a listener ... myService.adddisableStatisticsEventListener(myResultHandlingFunction); ... the listener's result function is called, but I have no token data from the AsyncToken/AsyncResponder. Could the problem be due to AsyncTokens being used within the Flex generated coded based off the WSDL? ie, wrapping AsyncToken calls around other AsyncToken calls? Tref