Since this is a "wrapped" doc/lit WSDL, it is expected that the request message will be treated as a sequence of parameters, and a Stub will be generated with a 1 argument function: echoString(String inputString).
I did this work for Axis 1.0. Fun stuff. I would say that to provide the minimum level of stub migration from Axis 1 to 2 that you guys are going to have to support the wrapping and unwrapping of parameters too. See the Axis 1.x file: o.a.a.wsdl.toJava.SymbolTable.java for the description and code for when it is OK to unwrap an operations parameters. The good news is that WSDL 2.0 specifies the RPC "style" which is explicitly designed for tools to detect when thay can do this unwrapping process. It would be great to get some implementation experience for this as we *think* we designed it right, and would love to be proven correct. Tom Jordahl Macromedia Server Development -----Original Message----- From: Aleksander Slominski [mailto:[EMAIL PROTECTED] Sent: Thursday, July 28, 2005 11:59 PM To: [email protected] Subject: Re: [Axis2] Testing databinding and generated code user is not sending a string but <element name="echoString"> <complexType> <sequence> <element name="inputString" type="xsd:string" nillable="true"/> </sequence> </complexType> </element> that is sequence with exactly one element that maps to EchoStringDocument (methos names is really irrelevant in doc/literal). alek
