Hard to say for sure without seeing the WSDL, but it looks like a Flex bug. I'd suggest posting a bug report and include a .NET sample that causes the bug to appear, along with WSDL, and the Flex project. Everything should be abbreviated to only include code necessary to reproduce the bug.
https://bugs.adobe.com/flex/ In the interim you can try changing your service to use List<T> instead of an Array and perhaps that will help work around the problem. Best regards, Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Dave Kong Sent: Wednesday, February 06, 2008 8:42 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: What are the available WSDL -> AS3/Flex code generators out there? Hm.. hit a problem with collection results. The [0] element always seem to be an ArrayCollection and the real results start at element[1]. result generated.webservices.ArrayOfUser (@7983241) [inherited] [0] mx.collections.ArrayCollection (@7983f41) [1] generated.webservices.User (@7acb549) [2] generated.webservices.User (@7a69d99) [3] generated.webservices.User (@7a896d1) [4] generated.webservices.User (@7acbba1) [5] generated.webservices.User (@7acbaf9) Is this a bug or is there something wrong with my WS? (I checked my WS and the raw stream does not contain extraneous data.
