--- In [email protected], "Peter Farland" <[EMAIL PROTECTED]> wrote: > > Hi Peter, > > Thankyou for logging that bug (although we require a WSDL and any > imported XML Schemas to be provided with any WebService bug logged, > would you mind adding that too?). >
I added that this morning. > You mentioned the response isn't handled as you wanted it. Did you add > further details in your bug about what you want the response to look > like as well? > Actually, it's the request that isn't handled properly. I included a bare-bones map that creates a request object that is what I would expect it to look like. The problem is that the SOAP message that Flex creates from the request is missing the array elements of the message. I included a TCPMon trace to show the request as it is received (sans arrays). I will also include a mock-up of what the full SOAP request should look like... > In general, when logging bugs, please try to stay with the latest > nightly builds of the SDK. Much work has been done since Beta 2 (and > note that Beta 3 was just released). Note that very recently (build > 189998) further properties were added to the ISOAPDecoder interface to > provide more control over how possibly-reoccuring result parts are > decoded in a response. The existing behavior was preserved, but when we > get more details about your response we'll be able to see whether you > can take advantage of these settings. > > Regards, > Pete > I downloaded Flex 3 Beta 2 Builder stand-alone and layered the latest SDK build onto that (190753) before clean building the app and running the tests. Up until yesterday I had been using Flex 2.0.1 w/Hotfix 3.
