Client (WebForm, WinForm, etc. Calling WebService)
One function module calls this WebService
In the calling process, first produce a proxy class on the client.
This proxy class encapsulates the parameters into SOAP and executes "communication" call.
Proxy class sends a SOAP request to the server and executes WebService on the server.
Returned XML streams Get the SOAP response by the Client's proxy class
Then give the CLIENT's current module
These are what I have learned before.
Today, I found that proxy can come out, then directly quote this proxy when writing applications.
Of course, this is not needed in .NET, but if you really want to do a cross-platform call
It is desirable because of the WebService on a .NET server on Linux.
Just do a proxy proxy class (at least I just think so now) in Linux.
Then Linux application can achieve call .NET WebService
Really. Net has a proxy class that has been written under .NET.
But there is some difficulty under Linux, or does not implement a .NET's WebService's Proxy Class
In this case, you cannot call .NET WebService with Java.
I only blame the development of Linux is too weak.
Looking forward to further Success ...
