Need help with C# SOAP Apache Client on Tomcat

Hi,

I am newbie to C# SOAP programming.I have a C# SOAP Apache Client that is calling a java webservice on Apache Tomcat 5.5.9 using SOAP (2.2.3) protocol.
The webservice works fine when I use a java client to call it. However i do not get a response back
from the C# client. Can someone help me out with this.

Here is the example that I have been trying to run http://www.c-sharpcorner.com/Code/2002/April/CSSoapApacheClient.asp

The only error that I see is An exception occurred while trying to create an instance of System.Web.Services.Protocols.SoapHttpClientProtocol. The exception was "WebServiceBindingAttribute is required on proxy classes.". in the design view of the proxy. My source code does have this declaration.

K, i figured out what I was doing wrong. The way java clients and c# clients interact with the same SOAP web service is totally different. This is mainly in terms of encoding and response retrieval.
Apache SOAP and .NET Framework-based Web services, by default, use different encoding and document styles. Apache SOAP Web services are typically RPC/Encoded, and .NET Framework-based Web services are typically Document/Literal.

The way I got around this issue was by using Apache Axis instead of Apache SOAP. Axis generates a WSDL for any web service deployed onto the server. This can be used as input to
the wsdl.exe tool available in .Net which then generates the proxy needed by .Net to access the service. Makes life much simpler.
Here are the links that I referred to:

http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html?page=2

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/ASPNet-JSPMig-WebServicesIntegration.asp

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Sohail Kagzi21y ago
K, i figured out what I was doing wrong. The way java clients and c# clients interact with the same SOAP web service is totally different. This is mainly in terms of encoding and response retrieval.
Apache SOAP and .NET Framework-based Web services, by default, use different encoding and document styles. Apache SOAP Web services are typically RPC/Encoded, and .NET Framework-based Web services are typically Document/Literal.

The way I got around this issue was by using Apache Axis instead of Apache SOAP. Axis generates a WSDL for any web service deployed onto the server. This can be used as input to
the wsdl.exe tool available in .Net which then generates the proxy needed by .Net to access the service. Makes life much simpler.
Here are the links that I referred to:

http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html?page=2

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/ASPNet-JSPMig-WebServicesIntegration.asp