Hi. I'm seeing this same behaviour (bug?) too, in a webservice using Java/Tomcat/XFire, and which seems OK from the Eclipse web service explorer test harness. Could you let us know whether you posted a bug to Adobe? If so, I will add my case to it.
Cheers, Tim --- In [email protected], "Samuel R. Neff" <[EMAIL PROTECTED]> wrote: > > 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/ > ... > > 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. >
