axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Created: (AXISCPP-257) <xsd:all> in WSDLs treated same as <xsd:sequence>
Date Thu, 11 Nov 2004 08:19:25 GMT
<xsd:all> in WSDLs treated same as <xsd:sequence> 
--------------------------------------------------

         Key: AXISCPP-257
         URL: http://nagoya.apache.org/jira/browse/AXISCPP-257
     Project: Axis-C++
        Type: Bug
  Components: Basic Architecture, WSDL processing  
    Versions: current (nightly), 1.3 Final    
    Reporter: Samisa Abeysinghe


>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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message