I advise setting resultFormat=”e4x”,
doing away with binding into the mx:Model, and instead using a result handler handler
to assign the result directly to an instance/global XML variable. This way, you can trace the contents of
event.result.toXMLString(), and see exactly what you have in Flex. Mx:Model converts the xml into a nested
mx:Object structure. Dumping its content is harder than toXMLString(). If you need a collection for a list-based
control dataProvider, use an e4x selection _expression_ to return an XMLList, and
wrap that in an XMLListCollection. From: All, I'm a Flex Newbie - coming from the Java world
(nice to not have -- 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
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___ |