[ http://issues.apache.org/jira/browse/AXISCPP-257?page=all ]
Dushshantha Chandradasa reassigned AXISCPP-257:
-----------------------------------------------
Assign To: Dushshantha Chandradasa
> <xsd:all> in WSDLs treated same as <xsd:sequence>
> -------------------------------------------------
>
> Key: AXISCPP-257
> URL: http://issues.apache.org/jira/browse/AXISCPP-257
> Project: Axis-C++
> Type: New Feature
> Components: Basic Architecture, WSDL processing - RPC
> Versions: current (nightly), 1.3 Final
> Reporter: Samisa Abeysinghe
> Assignee: Dushshantha Chandradasa
> Attachments: WS021A.wsdl
>
> From mailing list:
> Samisa->
> Can we expect the SOAP message to have the elements in the same order defined
> by the
> WSDL? If yes (I think it is) we are OK. If not we have another bug :(
> Adrian Smith ->
> If the schema says <xs:sequence> then yes, the order is expected to be
> correct, but not if it says <xs:all>
> Carsten->
> I also looked at <xsd:choice>, which also has arbitrary ordering of a finite
> choices. \
> My impression was that the generated stubs was not able to handle that at
> all. \
> Typically there would be something like a switch for all the possiblities.
> What I have seen to deal with cases like this is an intermediate structure
> between \
> parser and interpreting code where it is possible to push back the current
> element \
> back to have some other code handle it.
> See the mail thread http://marc.theaimsgroup.com/?t=109902729200001&r=1&w=2
> for more information
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
