axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brenda Bell <bb...@juicesoftware.com>
Subject RE: Axis Chokes on Complex Types from MS Soap 3.0
Date Tue, 06 Aug 2002 21:24:25 GMT
As best as I can tell, this looks perfectly legal and would be expected
behavior.  If the SOAP response indeed looks exactly like you've represented
it:

> ------------ SOAP-ENV Excerpt ----------------
> <myns:Mission xmlns:myns="http://blah/TestWebService/type/"
> xsi:type="myns:Mission">
> 	<MissionName>Some Mission Name</MissionName>
> 	<MissionNumber>42</MissionNumber> 
> </myns:Mission>
> ----------------------------------------------

Neither the MissionName nor MissionNumber elements are in a namespace...
that would explain why changing the QName to an unqualified name works.


Mime
View raw message