Hi there:

We've run into some webservice issues here when switching from Flex 
2.0.1 (not the hotfix version) to Flex 3. We are retrieving data from 
a .NET backend using a SOAP/wsdl format. When we switched to Flex 
3.0, the structures returned on the repsonse were sometimes a little 
different. 

For example, we had a data structure returned that was like this: 
data.result.UserProfileResponse.snapshots.Calendars
Where Calendars was an ArrayCollection.

Now the struture comes back without the Calendars part, and the data 
is in an ArrayCollection under the 
data.result.UserProfileResponse.snapshots structure.

The wsdl loks like this:
<![CDATA[

<s:complexType name="UserProfileResponse">
  <s:sequence>
    <s:element minOccurs="0" maxOccurs="1" name="userProfileDAO" 
type="tns:UserProfileDAO" />
    <s:element minOccurs="0" maxOccurs="1" name="snapshots" 
type="tns:ArrayOfCalendars" />
  </s:sequence>
</s:complexType>

<s:complexType name="ArrayOfCalendars">
  <s:sequence>
    <s:element minOccurs="0" maxOccurs="unbounded" name="Calendars" 
nillable="true" type="tns:Calendar" />
  </s:sequence>
</s:complexType>
]]>

Is this a result of the changes to implement e4x on webservices?
Has anyone else run into this issue?

Thanks in advance,
Mike


Reply via email to