Thanks for the reply.
My question though was, AXIS provides the api's to write clients for
document and the rpc based services. There are certain WSDL's with the
binding which reads like

<binding name="AddressLookupHttpPost" type="s0:AddressLookupHttpPost">
<http:binding verb="POST" />
<operation name="CheckAddress">
<http:operation location="/CheckAddress" />
.................
verb could be GET as well.

Axis provides API's to write clients for document/rpc based services. Does
it provide API's to write the client for POST/GET based services? I assume
no. How else can I invoke it then.
Moreover, if "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.  " is the way to attck the problem, then the
concept of web services (applications talking to each other without need for
user intervention) is jeopardised. Am I correct or I missed somthing here?

Sudhir



----- Original Message -----
From: "Andrew Vardeman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 17, 2002 2:32 PM
Subject: Re: Clients using GET and POST


> 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.
>
>
>
>

Reply via email to