Mike - I suppose I never actually tried -i. I was using Java2Wsdl on an interface, in which case -i doesn't help, but is -i required to retain param names from code built with debug info? If so, then perhaps that was Rey's problem (and future posters!). If that's the case then I'll know not to pounce on every "Param Name Retention" question with the No Debug Info In Interfaces spiel.
- C -----Original Message----- From: Michael Woinoski [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 1:58 PM To: [EMAIL PROTECTED] Subject: Re: Lost service method parameter names when deploying I've been using the Java2WSDL's "-i" option, and it retains the parameter names in the WSDL. "-i" takes the fully-qualified implementation class name as an argument (you still need to pass the interface as an argument to Java2WSDL). No need to hand edit the WSDL. -i, --implClass optional class that contains implementation of methods in class-of-portType. The debug information in the class is used to obtain the method parameter names, which are used to set the WSDL part names. (from AXIS_HOME/docs/reference.html#Java2WSDL) Cheers, Mike Chris wrote: > > Hi Rey, > > I went through this last week on the list. You can check the archives if you > like, for subject line="Preserving param names in WSDL". My issue, and > perhaps yours, is that parameter names for interface methods don't get saved > along with the debug info. Same goes for abstract methods in an abstract > class, by the way. > > If you want parameter names to be preserved, looks like you have the > following options: > > 1. Hand edit the WSDL to add them in > 2. Hand edit the WSDD (I forget the syntax but you can find it in the > archives) > 3. Screw Java2WSDL, and build your interfaces using an WSDL editor rather > than a Java editor. > -- Mike Woinoski Pine Needle Consulting mailto:[EMAIL PROTECTED]
