Thanks, that makes sense. I understand the workaround for getting the service to show the correct WSDL.
However, there seems to be a problem with the client codegen for rpc/literal. So far I have only managed to make it work correctly with parameter that has a simple type (I tried xs:string) When I change the type of the parameter to complex type, the client no longer adds the "part" element to the SOAP message it sends. Instead the "operation" element contains the complex data directly as if the SOAP message was a document literal style message. I am using the axis2 eclipse codegen plugin 1.1.1 with the default option (ie adb generation). I'll attach the WSDLs once I think I have a reproducible case Tim Amila Suriarachchi wrote: > > hi, > In codegeneration with wsdl, we convert the rpc style wsdl in to document > style (similar in messages) by generating the elements for rpc type > messages. And finally save the wsdl file to resource directory. When > saving > the wsdl file back it serializes the generated axis service object > structure > instead of saving the origianl wsdl as it is. That is the reason why you > get > a wsdl which is converted to document style. So can you please replace > your > saved wsdl in resource folder with the original wsdl and see. > On the other hand axis2 generates a wsdl only if the Message receiver is > one > of RPCMessageReceivers. but when generating the code from the wsdl it > creates a custom message receiver for the given wsdl file. > > Amila. > -- > Amila Suriarachchi, > WSO2 Inc. > > -- View this message in context: http://www.nabble.com/RPC-WSDL---Codegen--tf2593238.html#a9094660 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
