1 Reply Latest reply on Dec 19, 2007 6:17 AM by Peter Farland

    Problem mx:WebService with ActionWebService

    shimariso
      I have been using Flex Builder 3 for pretty often in my work.
      Last week new Flex Builder 3 beta 3 came up, I installed new Flex Builder 3 beta3.
      This program was usually working on Flex Builder 3 beta2,
      after I upgrade to beta3 to re-compile exact same program, doesn't receive any values any more.
      I believe this is bug on mx:WebService.

      This is SOAP response example.

      <?xml version="1.0" encoding="UTF-8" ?>
      <env:Envelope xmlns:xsd=" http://www.w3.org/2001/XMLSchema"
      xmlns:env=" http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance">
      <env:Body>
      <n1:SayHelloResponse xmlns:n1="urn:ActionWebService"
      env:encodingStyle=" http://schemas.xmlsoap.org/soap/encoding/">
      <return xsi:type="n1:MyStruct">
      <rslt xsi:type="xsd:string">Hello, aaa</rslt>
      </return>
      </n1:SayHelloResponse>
      </env:Body>
      </env:Envelope>

      Server side program is create by Ruby on Rails,using ActionWebService. This program is sending SOAP response that contains a struct. But,in Flex builder 3 beta 3's mx:WebService event.result doesn't receive any data. It seems recognize and events are happening, but inside value is always come up with "null".

      Thank you.
        • 1. Re: Problem mx:WebService with ActionWebService
          Peter Farland Level 3
          The best way to get help with WebService issues is to log a bug in JIRA against the Flex SDK: http://bugs.adobe.com/flex/

          When logging WebService issues, be sure to include the WSDL, any schema imports, a snippet of how the request is being made if there's a problem encoding the SOAP request, and a capture of the HTTP SOAP response XML if there's a problem with decoding (as there appears to be in your scenario below).

          I'd check the type of your event.result first. Make sure that you're not casting your result with the as operator to an incompatible type because you'll just get null instead of a coercion error.