|
If you were logged in you would be able to see more operations.
|
|
|
Flex SDK
Created: 01/13/08 01:16 PM
Updated: 08/05/08 03:57 PM
|
|
| Component/s: |
RPC: WebService
|
|
Security Level:
|
Public
(All JIRA Users
)
|
|
| Severity: |
Enhancement/Task
|
| Reproducibility: |
Every Time
|
| Discoverability: |
Medium
|
| Found in Version: |
SDK Flex 3 (Released)
|
| Milestone: |
SDK Flex 3.1.0
|
| Steps to Reproduce: |
As stated in https://bugs.adobe.com/jira/browse/SDK-14194 xsd:all elements in a web service response are treated as xsd:sequence elements, resulting in missing attributes in objects in web service responses.
A workaround was provided stating to use xsd:sequence elements and/or ensure that elements arrive in the predefined order, but this workaround may not be possible to perform if users are employing third party web services, or those backed by libraries or frameworks such as Ruby on Rails' ActionWebService and/or Ruby's SOAP4R.
It would therefore be useful if Flex followed the proper behaviour for xsd:all elements and allowed child elements to appear in any order.
As stated in https://bugs.adobe.com/jira/browse/SDK-14194 xsd:all elements in a web service response are treated as xsd:sequence elements, resulting in missing attributes in objects in web service responses.
A workaround was provided stating to use xsd:sequence elements and/or ensure that elements arrive in the predefined order, but this workaround may not be possible to perform if users are employing third party web services, or those backed by libraries or frameworks such as Ruby on Rails' ActionWebService and/or Ruby's SOAP4R.
It would therefore be useful if Flex followed the proper behaviour for xsd:all elements and allowed child elements to appear in any order.
|
| Language Found: |
English
|
| Bugbase Id: |
none
|
| Triaged: |
Yes
|
| Regression: |
No
|
| QA Owner: |
Bill Sahlas
|
| Resolved by: |
Peter Farland
|
| Fixed Version: |
SDK Gumbo Iteration 6
- Next Build
|
| Confirmed Version: |
SDK Gumbo Iteration 6
- Next Build
|
| Participants: |
Elliot Bowes, Joan Lafferty, Joann Chuang, Peter Farland and Steven Erat
|
As stated in https://bugs.adobe.com/jira/browse/SDK-14194 xsd:all elements in a web service response are treated as xsd:sequence elements, resulting in missing attributes in objects in web service responses.
A workaround was provided stating to use xsd:sequence elements and/or ensure that elements arrive in the predefined order, but this workaround may not be possible to perform if users are employing third party web services, or those backed by libraries or frameworks such as Ruby on Rails' ActionWebService and/or Ruby's SOAP4R.
It would therefore be useful if Flex followed the proper behaviour for xsd:all elements and allowed child elements to appear in any order.
|
|
Description
|
As stated in https://bugs.adobe.com/jira/browse/SDK-14194 xsd:all elements in a web service response are treated as xsd:sequence elements, resulting in missing attributes in objects in web service responses.
A workaround was provided stating to use xsd:sequence elements and/or ensure that elements arrive in the predefined order, but this workaround may not be possible to perform if users are employing third party web services, or those backed by libraries or frameworks such as Ruby on Rails' ActionWebService and/or Ruby's SOAP4R.
It would therefore be useful if Flex followed the proper behaviour for xsd:all elements and allowed child elements to appear in any order. |
Show » |
|
All
|
Comments
|
|
Sort Order:
|
|
Minor Enhancement
Closed
C
xsd:all elements should not be treated as xsd:sequence elements
