Here is a repost of my answer to the first question: According to the user guide: "Write and compile a Java interface (or class) that describes the web service interface. Note: If you compile your class with debug information, Java2WSDL will use the debug information to obtain the method parameter names. Use the Java2WSDL tool to create a WSDL file from the interface above."
So you want to compile your java file with the -g option so Java2WSDL can extract the parameter names. Although, even though the above says you can use an interface, you must use a class for it to correctly extract the parameter names. You could also use the -i option with Java2WSDL, but haven't tried that myself as it doesn't help much in my case (see below). My additional question is: Is this a bug in Java2WSDL or an error in the user guide? I hope this is a bug that will be fixed. I am creating a web service out of existing older code that can't be modified. In the process I am writing a new interface class for the web service that has different method names and parameters than the original code. I'd like to be able to use Java2WSDL against the interface, but instead I'm having to make it into a class with empty method bodies to work around this issue. -----Original Message----- From: Roslan Amir [mailto:[EMAIL PROTECTED] Sent: Monday, July 19, 2004 10:29 PM To: [EMAIL PROTECTED] Subject: Re: Parameters name, Helpers, Skeleton Hi, I will answer the first one. I'll let others answer the rest. I'm interested in the answers to those as well. When you generate WSDL from your interface, somehow Axis ignores your parameter names and uses in0, in1, etc. What I usually do is edit the WSDL file and changed all occurrences of in0 with parm1, in1 with parm2, etc. Then the classes generated from the WSDL will have your preferred names. Also, if you have a complex type for your parameters and/or the return type, the schema generated in the WSDL may rearrange the order of the fields. If the order is important to you, you have to edit the WSDL to put them in the correct order. Roslan Arnaud Vezain wrote: > Hello, > I'm writing web-services based on Axis and I have several problems. > > 1) When I write the interface of my RPC-Service I specify my own > parameters name. But when I generate the others classes of my service, my > initial interface is overwritten and the parameters name change to in0, > in1, etc. > Why? > > 2) What helpers can be used for ? > > 3) What is the advantage of deploying a skeleton-based service rather than > of an implementation-based one ? > > Arnaud. > > > > >
