On Jan 9, 2008 3:14 PM, keith chapman <[EMAIL PROTECTED]> wrote:

> If you generate code for a HTTPBinding (not a SOAPBinding) and it the
> httpBinding specifies that the HTTP method for that operation is GET then it
> will genarate code to do it.


use -pn <port name> -sn <service name> options to generate the code for a
pirticular port.
for wsdl 2.0 this should work fine.

Thanks,
Amila.

> Axis2 also supports PUT and DELETE.  PLease note that the HTTPBinding
> description of WSDL 1.1 is not that rich. I would recommend you to use
> WSDL 2.0.




>
> Thanks,
> Keith.
>
>
> On Jan 9, 2008 3:05 PM, Mauro Molinari <[EMAIL PROTECTED] >
> wrote:
>
> > Hello all!
> > We are using Axis2 in a client environment to invoke a web service.
> >
> > Looking at org.apache.axis2.transport.http.HTTPSender.HTTPSender() I see
> > that there can be a parameter set in the message context, created when
> > invoking an operation, that specifies whether Axis2 should use an HTTP
> > POST or HTTP GET method to send the request to the web service provider.
> > By default, it seems that WSDL2Java generates ADB code that doesn't
> > specify anything, so the default behaviour (line 77) of making an HTTP
> > POST request is chosen.
> >
> > My question is this: is there a way to specify to WSDL2Java to generate
> > client code that makes calls using HTTP GET method, or must I manually
> > modify the generated code to add the appropriate value for
> > org.apache.axis2.Constants.Configuration.HTTP_METHOD parameter to the
> > message context for each operation invocation method?
> >
> > Thanks in advance.
> >
> > --
> > Mauro Molinari
> > Software Developer
> > [EMAIL PROTECTED]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Keith Chapman
> Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org




-- 
Amila Suriarachchi,
WSO2 Inc.

Reply via email to