I have a program that calls a web service using the PEAR SOAP
extension. The problem is that on one machine it works and on another
it doesn't. The actual part of the conversation that specifies the
method to call and the parameters looks like this in the case where it
works:
<ns5:getCustome rInfoFromSID>
<ns5:sid>xxx</ns5:sid>
</ns5:getCustomer InfoFromSID>
And in the case where it doesn't work like this:
<ns5:getCustome rInfoFromSID>
<sid xsi:type="xsd:s tring">xxx</sid>
</ns5:getCustomer InfoFromSID>
The webservice fails and gives a message:
Error deserializing arguments.
Unrecognized element sid - expected sid@http://www.test.com/
Which kind of makes sense since there is no ns5 namespace on the
parameter. But why isn't there?
Any ideas would be much appreciated!
-- Mikael
extension. The problem is that on one machine it works and on another
it doesn't. The actual part of the conversation that specifies the
method to call and the parameters looks like this in the case where it
works:
<ns5:getCustome rInfoFromSID>
<ns5:sid>xxx</ns5:sid>
</ns5:getCustomer InfoFromSID>
And in the case where it doesn't work like this:
<ns5:getCustome rInfoFromSID>
<sid xsi:type="xsd:s tring">xxx</sid>
</ns5:getCustomer InfoFromSID>
The webservice fails and gives a message:
Error deserializing arguments.
Unrecognized element sid - expected sid@http://www.test.com/
Which kind of makes sense since there is no ns5 namespace on the
parameter. But why isn't there?
Any ideas would be much appreciated!
-- Mikael
Comment