Are you using 2.0.1? There were a handful of WebService serialization/deserialization issues resolved, some of which were specific to .NET services.
You might also want to check out Darron Schall's ObjectTranslator class: http://www.darronschall.com/weblog/archives/000247.cfm. HTH, Ben --- In [email protected], "herrodius" <[EMAIL PROTECTED]> wrote: > > Hi all, > > we are currently creating a series of webservices to talk to our .Net > backend system. We are sending over nested value objects which > sometimes contain nested arrays of objects. When we receive an array > in Flex, it is mapped to an ArrayCollection. We then have to do the > actual object mapping manually, which is the way to go I suppose. > > But when we send over nested arrays, the first array is converted to > an ArrayCollection successfully but every other (deeper) array is > converted to an ObjectProxy in which there is an ArrayCollection that > contains the actual data of the Array. There seems to be an extra > object/level that gets created. > > An example (debugger output): > > result (ObjectProxy) > - Components (ArrayCollection) > -- [0] (ObjectProxy) > -- [1] (ObjectProxy) > --- Answers (ObjectProxy, should be ArrayCollection) > ---- GapAnswer (ArrayCollection, does not exist in the original object > and should not be here) > ----- [0] > ----- [1] > > As you can see there is an "Answers" property in the second item of > the "Components" ArrayCollection. This should be an ArrayCollection > instead of an ObjectProxy and the "GapAnswer" property in it should > not even exist. (GapAnswer is the type of the .Net Answers array -> > GapAnswer[] Answers) > > Has anyone run into this before? Could this be a bug in the > deserialization of the objects? > > regards, > Christophe >
