What might be contributing to the confusion is the fact that Microsoft has built in HTTP GET-based access to its .NET webservices. Request the service via HTTP GET and you are presented with an HTML form with input fields for the parameters. You submit the form (also via HTTP GET) to the webservice, and it responds with a SOAP envelope. This is a trick that really has nothing to do with SOAP; the .NET client is acting as a miniature web server, and when you submit the form, the parameters are passed to the webservice in the URL as though the service were an ordinary CGI program or server page. If you want to make this kind of "web service," you could do it with ASP or JSP just as easily as with a SOAP toolkit.
Andrew > > Hi All, > > How do I write a client which is HTTP GET/POST based? > > Do I have to create a SOAP request document and send it using the >GET/POST? > > If I POST it, then it is same as the SOAP document based client. > > > How can send the entire SOAP request XML as GET? > >firstly, you have to rewrite the bit of the HTTP specification that says >'you cant send a body in a GET request', call it say HTTP1.2 for want of a >better name > >secondly you need to change all the firewalls, web servers and client >implementations to support this > >thirdly you need to add the support to axis > >Personally, I'd stick with POST.
