Re: Clients using GET and POST

[Rozi Kovesdi <r....@verizon.net>]

Sudhir,

I have the same questions you had a while back -
Have you find the answer?
I want to understand if Axis can be used for "ordinary" HTTP POST w/o SOAP?

As a test, I gave a WSDL file to the WSDL2Java program which had http binding
and verb=POST
but the output java code was still a SOAP  rpc service

Is it possible to use WSDL2java to generate correct  java code for an  HTTP POST
binding?
i.e.
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"

I haven't been successful
Is this a bug, or am I missing something?

thank you
Rozi

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