Those two are actually different soap messages.
The major difference is that first one uuid/label has no namespace,
but the second one uuid/label has namespace http://modalities.services.gitta.tentelemed.com/
Freeman
On 2011-6-30, at 下午9:23, Anthony Webster wrote:
Hello,
Could someone explain why the following works :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
" xmlns:mod="http://modalities.services.gitta.tentelemed.com/";>
<soapenv:Header/>
<soapenv:Body>
<mod:GetResultsCount>
<uuid>v</uuid>
<label>fd</label>
</mod:GetResultsCount>
</soapenv:Body>
</soapenv:Envelope>
whereas this doesn't :
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"; >
<s:Body>
<GetResultsCount xmlns="http://modalities.services.gitta.tentelemed.com/
">
<uuid a:nil="true" xmlns:a="http://www.w3.org/2001/XMLSchema-
instance"/>
<label a:nil="true" xmlns:a="http://www.w3.org/2001/XMLSchema-
instance"/>
</GetResultsCount>
</s:Body>
</s:Envelope>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
<soap:Body>
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>Unmarshalling Error: unexpected element (uri:"
http://modalities.services.gitta.tentelemed.com/";, local:"uuid").
Expected
elements are <{}label>,<{}uuid></faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Is there a way to ensure that calls like the second one can work?
Thanks,
Anthony
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
