If you have control of the web service itself and no one is forcing you to use SOAP you have other less complex, better performing options.
1) If you want to use XML, try using REST style web services or a straight XML representation of your object and you can explicitly control how you read/write the object(s), 2) If you have some Ajax code that might call it also, you might consider using JSON, 3) But the best solution if your client is Flex and will most likely always be Flex (in my opinion) is to use AMF. I know that Flex supports SOAP web services but after working for a while with fairly complex SOAP web services using Java tools but having to play well with .NET generated solutions convinced me that complexity for the sake of complexity (SOAP) is going to make your life harder no matter what tools you use. But I understand if you have some 'architect' or manager telling you that you MUST use SOAP. Been there... $0.02 Good luck! - Todd --- In flexcoders@yahoogroups.com, "christophertholen" <[EMAIL PROTECTED]> wrote: > > Hi, > > I am having trouble with the Flex decoding of complex soap objects. > The mxml is validated and looks fine, but the object structure is > quite complex and Flex seem to have a lot of trouble decoding the > objects I send from the server. > > An example would be a returnobject, containing the status of a call, a > description string and the result array of complex objects. > > The Flex SOAPdecoder does not seem to be able to decode the array of > complex objects. > > > Do you know if there is any solution to this? > If there is not a solution, is it because having nested complex > objects is not recommended for web services? > Would a flat object layer be a better and faster solution even though > it pollutes the server structure a lot? > > > > Thanks, > Chris >
