axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Franz Fehringer <...@isogmbh.de>
Subject Re: order of returned elements
Date Thu, 25 Jan 2007 09:12:05 GMT
Only if xsd:all is in effect (but note that i am not a real XSD expert).

Franz


Nicholas Hart schrieb:
>
> I have a question regarding how AxisCPP parses a response.  It's my 
> understanding that the order of the elements shouldn't matter, eg:
>
> <myobj>
>     <foo>hello</foo>
>     <bar>world</bar>
> </myobj>
>
> should be equivalent to:
>
> <myobj>
>     <bar>world</bar>
>     <foo>hello</foo>
> </myobj>
>
> however, in the stub client code generated by AxisCPP, the order 
> definitely matters.  if the order elements are returned doesn't match 
> up to the order in which the stub tries to parse them, an error is set 
> and the rest of the object fails to parse.
>
> I've been manually changing a bunch of my stub code to parse the order 
> returned by our server.  however, this is a big pain and I fear that 
> if the order changes it will break my client.
>
> Is this a known issue with AxisCPP?  It seems like this could be fixed 
> by generating stubs that iterating through the elements in the 
> response, peek at their names and then invoke the appropriate parsing 
> code for each element.  Or perhaps this should go into AxisCPP so that 
> getElement() doesn't look for the next element, but instead finds the 
> named element.
>
> thoughts?  comments?
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>


Mime
View raw message