In Flex 2, mx.rpc.events.ResultEvent is a subclass of mx.rpc.events.AbstractEvent which still contains a deprecated getter for a call property. The new name for this property is token (as per the dynamic mx.rpc.AsyncToken instance that is returned from any RPC service invocation).

I'm not familiar with Cairngorm, but you can also assign invocation specific responders to AsyncTokens. I think by beta 3 this had become potentially many responders so the API on this call/token changed from a token.responder property to token.addResponder(r:IResponder):void. This means that the responder must implement mx.rpc.IResponder.



-----Original Message-----
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Iuliu Burtoiu
Sent: Friday, May 19, 2006 8:42 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Cairngorm - <mx:HTTPService result="event.call.resultHandler( event )"... doesn't work anymore

Hello again!

I'm trying for some time now, to add a custom webService in my Services.mxml control.

However, the "dummyDelegate" HTTPService from the old version of Cairngorm LOGIN sample doesn't seem to work anymore with Flex 2b3.

More specific, it seems that there isn't a "call"
property on the event:ResultEvent anymore.

So, any ideas how could I link the result handler from a <mx:HTTPService> with the  responder's "onResult"?

Thanks

Iuliu

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around http://mail.yahoo.com






--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links









--
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
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to