This is a typical .NET vs. PHP interop problem, and happens because the
.NET services (or clients) expect the payload to be namespace qualified
as you have figured out.
I too have looked into this with PHP SOAP extension, and what I gathered
is that the WSDL mode implementation needs to pick the qualifying
namespace and make that the default namespace of payload.
However, I could not locate the exact point in C code to fix this.
Samisa...
Michael Gross wrote:
Hi
I have a similar problem, only the other way round: the server is PHP,
the client is C#. I found that the problem is that the
xmlns="https://api.authorize.net/soap/v1/";
in the "AuthenticateTest"-tag is needed.
I tried to modify the PHP source code, but I had no success yet (it
would be fantastic, if someone could give me a hint where the XML
representation is built).
Michael
Tim Traver wrote:
The problem that I have is that the server that I am talking to (that
is not in my control), will accept the following SOAP call
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
<soap:Body>
<AuthenticateTest xmlns="https://api.authorize.net/soap/v1/";>
<merchantAuthentication>
<name>name</name>
<transactionKey>string</transactionKey>
</merchantAuthentication>
</AuthenticateTest>
</soap:Body>
</soap:Envelope>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
