(Note that this is Flex 2 Beta)
We didn't want the parent mx.rpc.soap.WebService to introduce extraneous
dependencies on other parts of the Application framework. So any
functionality that does introduce such a dependency (such as busy
cursors or bubbling of events to top level application handlers) must go
in this subclass.
You can use the mx.rpc.soap.mxml.WebService API in ActionScript too, you
just have to call
public function initialized(document : Object, id : String)
:void
(see the ASDoc for this class for more detail).
Pete
-----Original Message-----
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of ben.clinkinbeard
Sent: Tuesday, April 18, 2006 4:08 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] mx.rpc.soap.mxml.WebService VS
mx.rpc.soap.WebService
Why are these separate classes? More importantly, why does the mxml
version have capabilities that its super class does not? I like the
showBusyCursor functionality, but prefer to code in AS when possible.
Am I correct in assuming that these two things are mutually exclusive?
Thanks,
Ben
--
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
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
