Thanks Marcus that was my problem.
Sagar, I am not sure if you are having the same problem I was, but I needed to supply Java2WSDL with a class, not an interface.
Other than that, I don’t know where you would have a problem.
-Curt
-----Original Message-----
Can you elaborate on this please.
I face the same problem. In a message earlier, I was told that I can see the parameter names if I compile my classes using debug and then wsdl2java will be able to get the parameter names.
I run my wsdl2java on dynamically available wsdls from a running server. I can’t run my production system with debug jars. So how do I get around this problem and get parameter names in my proxies?
The implementation class that you mention should be on my server, which in my case is the same class available in my jars. Do I create a separate class? At the moment I delete the String “SOAPBindingSkeleton” from my server-config.wsdd file and restart my server, because there is no such file on my server.
Regards
Sagar
-----Original Message-----
To have java2wsdl use the method parameter names you need to supply the implementation class. It reads the param names from the implementation.
marcus
|
Title: Message
- RE: Java2WSDL ant task not keeping method param names Curt P. Stanton
- RE: Java2WSDL ant task not keeping method param name... Sagar Pidaparthi
- RE: Java2WSDL ant task not keeping method param name... Sagar Pidaparthi
- RE: Java2WSDL ant task not keeping method param ... Curt P. Stanton
- RE: Java2WSDL ant task not keeping method param name... mmosttler