Datelin, Thanks for your detailed response. It's really helpful. I am new to these things; one newbie question comes to my mind.
If I have a third party service which gives me RPC-encoded wsdl; does it mean I can't write axis2 client for that service and have to choose some other webservice utility? Or I can change the wsdl to rpc/literal and create stub and be able to talk to the 3rd party service. Thanks for your patience. On 8/21/08, Detelin Yordanov <[EMAIL PROTECTED]> wrote: > > Hi Shovan, > I think that Axis2 does not support rpc-encoded. It supports rpc-literal > WSDLs, but converts them to doc-lit wrapped on deploy. > However, we have found out that it is possible to deploy a service with > rpc-encoded WSDL on Axis2 1.4. > But you will need to write your own message receiver to do the > serialization/deserialization of SOAP-enc types. > You can create an aar containing the service and the rpc-encoded WSDL, and > instruct Axis2 to return your WSDL when clients ask for it (using the > "useOriginalwsdl" parameter in the services.xml). > > However, the tricky part is writing the message receiver which should be > able to handle SOAP-encoding types and convert them to Java types (and vice > versa). > > Regards, > Detelin > > On Thu, Aug 21, 2008 at 5:49 PM, Shovan Kanjilal < > [EMAIL PROTECTED]> wrote: > >> Can anybody point me to an example of rpc encoded sample wsdl and how stub >> is generated >> from that and an example client written? >> >> I see all the examples are document type? >> >> Does axis2 not support rpc-encoded? >> > >
