[EMAIL PROTECTED] Mon Apr 05 13:59:48 2004 Return-Path: <[EMAIL PROTECTED]> X-Sender: [EMAIL PROTECTED] X-Apparently-To: [email protected] Received: (qmail 59561 invoked from network); 5 Apr 2004 20:59:48 -0000 Received: from unknown (66.218.66.172) by m17.grp.scd.yahoo.com with QMQP; 5 Apr 2004 20:59:48 -0000 Received: from unknown (HELO p01mgw01.macromedia.com) (216.104.212.90) by mta4.grp.scd.yahoo.com with SMTP; 5 Apr 2004 20:59:48 -0000 Received: from s2009exm02.macromedia.com (s2009exm02.macromedia.com [10.176.24.87]) by p01mgw01.macromedia.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id i35Kxl5I020433 for <[email protected]>; Mon, 5 Apr 2004 13:59:47 -0700 (PDT) Received: by s2009exm02.macromedia.com with Internet Mail Service (5.5.2657.72) id <H74CW8N3>; Mon, 5 Apr 2004 13:59:23 -0700 Message-ID: <[EMAIL PROTECTED]> To: "'[email protected]'" <[email protected]> Date: Mon, 5 Apr 2004 13:59:12 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-eGroups-Remote-IP: 216.104.212.90 From: Matt Chotin <[EMAIL PROTECTED]> Subject: RE: [flexcoders] Flex and .NET X-Yahoo-Group-Post: member; u=180540726 X-Yahoo-Profile: m_chotin
Those look great! Something for folks 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=3D"Login"> <part name=3D"UserId" type=3D"xsd:string" />=20 <part name=3D"Password" type=3D"xsd:string" />=20 <part name=3D"TokenResponse" type=3D"xsd:anyType" />=20 </message> <message name=3D"LoginResponse"> <part name=3D"Result" type=3D"xsd:int" />=20 <part name=3D"TokenResponse" type=3D"xsd:anyType" />=20 </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=3D"xml" on your operation tag and handle the parsing of the XM= L yourself. We'll be looking into fixes for this in a future version. Matt -----Original Message----- From: Andrew Stopford [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 1:44 PM To: [email protected] Subject: [flexcoders] Flex and .NET Hi, =A0 For any of you that may be using .NET and Flex take a look. =A0 http://weblogs.asp.net/astopford/archive/2004/04/05/107786.aspx =A0 Andrew =20
