Flex and .Net

For those who are watching the flexcoders mailing list, this information maybe a repitition. For all others, Something to note is that some .NET web services are written with multiple outputs. The one I recently saw had a WSDL signature like this:

<message name=”Login”>
<part name=”UserId” type=”xsd:string” />
<part name=”Password” type=”xsd:string” />
<part name=”TokenResponse” type=”xsd:anyType” />
</message>
<message name=”LoginResponse”>
<part name=”Result” type=”xsd:int” />
<part name=”TokenResponse” type=”xsd:anyType” />
</message>

In this case there are two “outputs”, Result and TokenResponse. Unfortunately the Flex WebService library does not deserialize multiple outputs correctly, so only the contents of Result end up getting deserialized. If you want to use a service like this you’ll need to set resultFormat=”xml” on your operation tag and handle the parsing of the XML yourself.

Macromedia Team will be looking into fixes for this in a future version.