PHP interoperation, SOAP, Webservice

H

Heiko

Contributor
Joined
Feb 10, 2003
Messages
430
Location
Holstein, Germany.
Sorry, this is not exactly an ASP question, but here it goes:

We have developed a Webservice in .NET. Our partner side uses PHP to access the webservice. It looks as if the WSDL is read fine, but when the partner side calls a webservice, all input parameters are empty.
The SOAP log on their side, however, shows that the parameters are present.

Has anyone ever experienced this ?

Here's their transcript:


OUTGOING:

POST /xxxxxx/xxxxxxx.asmx HTTP/1.0
User-Agent: PEAR-SOAP 0.7.3-devel
Host: web01.xxxxxxx.de
Content-Type: text/xml; charset=UTF-8
Content-Length: 655
SOAPAction: "http://www.xxxxx-interface.de/UpdateStatus"

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns4="http://www.xxxxx-interface.de/"
>
<SOAP-ENV:Body>

<ns4:UpdateStatus>
<DirectionCode>O</DirectionCode>
<Id>1304</Id>
<OrganizationCode>XXX</OrganizationCode>
<StatusCode></StatusCode>
<NewStatusCode>ERROR</NewStatusCode>
<xmlMessage></xmlMessage>
<xsdSchemaCode>DKIN0100</xsdSchemaCode></ns4:UpdateStatus>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Click to expand...
 
Addendum

The outgoing side (php) has this in the header ...

POST /xxxxxx/xxxxxxx.asmx HTTP/1.0


whereas on the sample html page generated by the webservice it reads

POST /xxxxxx/xxxxxxx.asmx HTTP/1.1


Does anyone know about the effects ?

Thanks.
 
I have done some more research.

Apparently, .NET by default expects "document/literal" SOAP documents, whereas most PHP versions rather prefer "rpc/encoded".

Can that be the problem ?

Is the sample above "document/literal" ?

Help!
Please ... (he muttered desperately)
 
Back
Top