I second that, but also thanks to you Ben!

 

Cheers,

Franck

 


From: [email protected] [mailto:[email protected]] On Behalf Of ben.clinkinbeard
Sent: Tuesday, September 05, 2006 6:24 PM
To: [email protected]
Subject: [flexcoders] Re: Confirmed Bug: SOAP request construction with .NET web service... again

 

Just minutes after posting my last message I received another email
from Adobe confirming that engineering is working on fixes to all 3
bugs I've encountered while dealing with .NET web services. They've
assured me that they'll be fixed in the first update release for Flex
2 and possibly even sooner via a hotfix.

It really is encouraging to see Adobe's willingness and ability to
make improvements and ensure Flex is as rock solid as possible. Thanks
Adobe!

Ben

--- In [EMAIL PROTECTED]ups.com, "ben.clinkinbeard"
<ben.clinkinbeard@...> wrote:
>
> Just for the sake of record, Adobe has just notified me that this is
> indeed a bug. I sure hope some WebService fixes are in that dot
release...
>
> Ben
>
> --- In [EMAIL PROTECTED]ups.com, "ben.clinkinbeard"
> <ben.clinkinbeard@> wrote:
> >
> > I have already come across a couple of (confirmed by Adobe support)
> > bugs with the way Flex constructs SOAP requests when using .NET web
> > services and am wondering if I've found a third. I suppose this could
> > be the expected behavior but it seems awfully weird to me. Part of the
> > request that my web service expects is a ContainersToRetrieve node,
> > which contains 1 or more child ContainerType nodes. Like this:
> >
> > <ContainersToRetrieve>
> > <ContainerType>IndustryTrends</ContainerType>
> > <ContainerType>RPRSelections</ContainerType>
> > </ContainersToRetrieve>
> >
> > When constructing the request in MXML, I have discovered that if I am
> > only sending one ContainerType argument that I need to omit the
> > ContainerType node and put the contents directly inside
> > ContainersToRetrieve. Like this:
> >
> > <ContainersToRetrieve>
> > IndustryTrends
> > </ContainersToRetrieve>
> >
> > But if I need to send more than one I have to include the
> > ContainerType nodes in my MXML, like this:
> >
> > <ContainersToRetrieve>
> > <ContainerType>
> > IndustryTrends
> > </ContainerType>
> > <ContainerType>
> > RPRSelections
> > </ContainerType>
> > </ContainersToRetrieve>
> >
> > Is this how this should work? I am including my entire WebService tag
> > below. Thanks in advance.
> >
> > Ben
> >
> > <mx:WebService id="ws" wsdl="http://mysite.com/WebService.asmx?WSDL"
> > useProxy="false"
> > fault="getTrendsFault(event)" result="getTrendsResult(event)">
> >
> > <mx:operation name="GetDocument" resultFormat="e4x">
> > <mx:request>
> > <EnterpriseId>11111</EnterpriseId>
> > <DocumentType>RPR-EBD</DocumentType>
> > <ContainersToRetrieve>
> > <ContainerType>
> > IndustryTrends
> > </ContainerType>
> > <ContainerType>
> > RPRSelections
> > </ContainerType>
> > </ContainersToRetrieve>
> > <MetadataToRetrieve>
> > RPRDocumentHistory
> > </MetadataToRetrieve>
> > </mx:request>
> > </mx:operation>
> > </mx:WebService>
> >
>

__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





SPONSORED LINKS
Software development tool Software development Software development services
Home design software Software development company


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to