[EMAIL PROTECTED] Tue Apr 06 04:55:55 2004 Return-Path: <[EMAIL PROTECTED]> X-Sender: [EMAIL PROTECTED] X-Apparently-To: [email protected] Received: (qmail 50737 invoked from network); 6 Apr 2004 07:01:25 -0000 Received: from unknown (66.218.66.172) by m1.grp.scd.yahoo.com with QMQP; 6 Apr 2004 07:01:25 -0000 Received: from unknown (HELO TRILLIAN.Herrlich-Ramuschkat.de) (193.218.214.132) by mta4.grp.scd.yahoo.com with SMTP; 6 Apr 2004 07:01:25 -0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 Date: Tue, 6 Apr 2004 08:58:49 +0200 Message-ID: <[EMAIL PROTECTED]> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [flexcoders] Flex and .NET Thread-Index: AcQbUJgteFzTjuRyQ2i1DC3lEhSGJAAUrzWQ To: <[email protected]> X-eGroups-Remote-IP: 193.218.214.132 From: "Dirk Eismann" <[EMAIL PROTECTED]> Subject: WebService Feature Request WAS: Flex and .NET X-Yahoo-Group-Post: member; u=166410723
If the team is already thinking about fixes please consider this also: In real-world WebServices (esp. those generated with AXIS or a .NET framework) you'll often find overloaded methods in the WSDL. Right now Flex can't handle this. Technote: http://www.macromedia.com/support/flex/ts/documents/mthd_overload.htm It really is Not A Good Thing (tm) if you have to call the Java guy who coded the WebService with all the overloading stuff and beg for a complete change of the code because Flex can't handle it ("oh, so it's that Flash thingy, eh?"). Happened to me once with a Flash 7 project (no Flex involved) - not funny. So - one vote from me for this one! And if youre on it: put it in the Flash Player, too :) Thanks, Dirk. > -----Original Message----- > From: Matt Chotin [mailto:[EMAIL PROTECTED] > Sent: Monday, April 05, 2004 10:59 PM > To: '[email protected]' > Subject: RE: [flexcoders] Flex and .NET >=20 >=20 > Those look great! >=20 > Something for folks to note is that some .NET web services=20 > are written with > multiple outputs. The one I recently saw had a WSDL=20 > signature like this: >=20 > <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> >=20 > In this case there are two "outputs", Result and TokenResponse. > Unfortunately the Flex WebService library does not=20 > 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=20 > need to set > resultFormat=3D"xml" on your operation tag and handle the=20 > parsing of the XML > yourself. >=20 > We'll be looking into fixes for this in a future version. >=20 > Matt >=20
