There should be classes generated by the tool that map to the types in the
WSDL, and then the actual webservice response has to match the types in the
WSDL. If there is some discrepancy, the conversion will not happen
Also, the generated classes must be linked into the SWF. If you comment
them out of your code somehow, then they won't be available for the
conversion. Generate a link-report and make sure they are in.
You might also have trouble if you do not use the generated WebService and
go directly to mx:WebService.
All the classes are generated. The classes for the complex type have been generated, and have not been touched.
I'm also using the generated service class to call the service.
Additionally, we're using the Cairngorm 2 framework.
Use a link-report to make sure they are in the SWF.
If they are, then start examining the WSDL and the SOAP response. See if
the class name is correct.
Link report shows all files are in the swf. I'm looking over the WSDL to see if there are any problems there.
The WSDL was used to generate the classes. What is now important is that
the type description in the SOAP response matches the definitions in the