« Hide

Steps to reproduce:
1. Call a web service that finds matching project names and produces the following SOAP message:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:mb="urn:ProjectService:1.0">
<SOAP-ENV:Body>
<mb:GetProjectNamesResponse>
<projectNameCount>
270
</projectNameCount>
<projectNames>
<name>
Test
</name>
<name>
Test86
</name>
<name>
TestPrj46267
</name>
</projectNames>
</mb:GetProjectNamesResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


 
 Actual Results:
 
[ResultEvent messageId="F91FAE9A-8B3C-3893-CCF1-D814B789097F" type="result" bubbles=false cancelable=true eventPhase=2]

Converting the result to XML produces:

[object Object]

 
 Expected Results:
 
 
 Workaround (if any):
 
 Interestingly, SOAP messages that have arrays of complex types or use the older style array (with "items") syntax work fine. The difference in this failure case is that the array is made up of simple types (string). The only workaround I've found is to respond with complex types (add an unnecessary element to each index in the array):

<name>...</name>

would need to be:

<ProjectName>
    <name>MyProject</name>
    <description>Element used to workaround Flex issue.</description>
</ProjectName>
 

Show »

Steps to reproduce: 1. Call a web service that finds matching project names and produces the following SOAP message: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:mb="urn:ProjectService:1.0"> <SOAP-ENV:Body> <mb:GetProjectNamesResponse> <projectNameCount> 270 </projectNameCount> <projectNames> <name> Test </name> <name> Test86 </name> <name> TestPrj46267 </name> </projectNames> </mb:GetProjectNamesResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope>    Actual Results:   [ResultEvent messageId="F91FAE9A-8B3C-3893-CCF1-D814B789097F" type="result" bubbles=false cancelable=true eventPhase=2] Converting the result to XML produces: [object Object]    Expected Results:      Workaround (if any):    Interestingly, SOAP messages that have arrays of complex types or use the older style array (with "items") syntax work fine. The difference in this failure case is that the array is made up of simple types (string). The only workaround I've found is to respond with complex types (add an unnecessary element to each index in the array): <name>...</name> would need to be: <ProjectName>     <name>MyProject</name>     <description>Element used to workaround Flex issue.</description> </ProjectName>