axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Riggs, David" <>
Subject RE: Axis Chokes on Complex Types from MS Soap 3.0
Date Wed, 07 Aug 2002 13:59:02 GMT
Full SOAP response:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<SOAP-ENV:Envelope xmlns:SOAPSDK1=""
			<Result href="#id1"/>
xmlns:SOAPSDK5="" id="id1"
SOAPSDK3:root="0" SOAPSDK2:type="SOAPSDK5:Mission">
			<MissionName>Some Mission Name</MissionName>

Should MissionName and MissionNumber be coming across the
wire with a namespace and type attached?

-----Original Message-----
From: Brenda Bell [] 
Sent: Tuesday, August 06, 2002 5:24 PM
To: ''
Subject: RE: Axis Chokes on Complex Types from MS Soap 3.0

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.

View raw message