|
Hi, All,
This problem really frustrates me. Even though it looks more like a .NET WS support problem than AXIS problem I post it here in hoping that AXIS developers have used .NET clients and may provide me suggestions to address the issue.
I have a AXIS web service running as the server and I have a client in C# communicating to the server. Using TCPMonitor I can tell that request an response both went fine. The response soap message corresponding to a logout action is as below.
<?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <Response xmlns="urn:messages.webservices"> <status> <code>SUCCESS</code> </status> </Response> </soapenv:Body> </soapenv:Envelope>
Clearly the response is NOT null. But .NET c# client did not recoganize the “status” element and claimed that the “status” object is “null”. This is the code:
// !!! logout MyService nss = new MyService(); Status logoutStts = new Status(); logoutStts = nss.logout(); if (logoutStts == null) richTextBox1.Text = "logout status is null";
It claimed that logoutStts is null. I appreciate any feedback or suggestion.
Thanks,
Scott Liu
|
